Add support for FST (fast signal trace) files #7

New issue

Open

opened 2022-10-28 19:33:31 +00:00 by alanvgreen · 3 comments

alanvgreen commented

2022-10-28 19:33:31 +00:00

(Migrated from github.com)

The FST format is often used when working with large traces. It is more compact and faster than VCD.

https://github.com/semify-eda/fstdumper is an FST reader/writer library.

The FST format is often used when working with large traces. It is more compact and faster than VCD. https://github.com/semify-eda/fstdumper is an FST reader/writer library.

ThePerfectComputer commented

2022-10-28 19:49:33 +00:00

(Migrated from github.com)

Yes, support for FST is being considered. One thing I'd really like to do however is keep only Rust code in the codebase.

How hard would it be to convert fstdumper to Rust, if I were to use fstdumper as a reference for a Rust version?

Yes, support for FST is being considered. One thing I'd really like to do however is keep only Rust code in the codebase. How hard would it be to convert fstdumper to Rust, if I were to use fstdumper as a reference for a Rust version?

alanvgreen commented

2022-10-28 20:07:52 +00:00

(Migrated from github.com)

I'm sure you'll have a better idea than me about how much effort it is.

It would be less effort to wrap the C, of course :)

I'm sure you'll have a better idea than me about how much effort it is. It would be less effort to wrap the C, of course :)

oscargus commented

2023-09-13 11:28:26 +00:00

(Migrated from github.com)

FYI, there is an alternative library for FST (released after this was opened): https://docs.rs/fstapi/latest/fstapi/

(Although, naturally, it would be nice to have the same API etc independent of underlying file format.)

FYI, there is an alternative library for FST (released after this was opened): https://docs.rs/fstapi/latest/fstapi/ (Although, naturally, it would be nice to have the same API etc independent of underlying file format.)