01-06-2014, 05:44 PM
Jeff, did you get the last version of the .scp file specification where I now allow for unlimited number of revolutions? It shouldn't break anything in your code if you are using the offsets. My code didnt break with the changes.
I would like to propose using .scp image files as a wrapper for all flux dumped images by making the reserved word in the header (0x00A-0B) the actual flux capture frequency (a base time, the minimum time per bit cell). This base time value would be multiplied by 100. So, SCP's 25ns flux times would give you a value of 2500. Kryoflux's 41.66ns flux times would give you a value of 4166. The Discovery Cartridge's 66.66ns flux times would give you a value of 6666. There are a couple of other flux copiers, one that is FPGA based and uses a 10ns capture, giving you a value of 1000. Using this method, ALL of the different flux copier's flux data could be stored in the .scp file format and then universally used. In your case, the only change you would make to your existing .scp support would be to look at the base time word and use that info as your multiplier for flux timing. To maintain backwards compatibility, any base time of 0x0000 would default to a value of 2500. It would be easy enough for me to convert any flux data contained within the image file to the proper timing for writing out to disk, no matter what flux device originally created the data. Your Thoughts?
I would like to propose using .scp image files as a wrapper for all flux dumped images by making the reserved word in the header (0x00A-0B) the actual flux capture frequency (a base time, the minimum time per bit cell). This base time value would be multiplied by 100. So, SCP's 25ns flux times would give you a value of 2500. Kryoflux's 41.66ns flux times would give you a value of 4166. The Discovery Cartridge's 66.66ns flux times would give you a value of 6666. There are a couple of other flux copiers, one that is FPGA based and uses a 10ns capture, giving you a value of 1000. Using this method, ALL of the different flux copier's flux data could be stored in the .scp file format and then universally used. In your case, the only change you would make to your existing .scp support would be to look at the base time word and use that info as your multiplier for flux timing. To maintain backwards compatibility, any base time of 0x0000 would default to a value of 2500. It would be easy enough for me to convert any flux data contained within the image file to the proper timing for writing out to disk, no matter what flux device originally created the data. Your Thoughts?