Replies: 10 comments
-
Here is a picture of the strings used when the recipe is converted to a CSV file.
|
Beta Was this translation helpful? Give feedback.
-
Here is the next part of the sequence when when CSV writing mode: |
Beta Was this translation helpful? Give feedback.
-
Here is the front panel which summarizes the values that are read or written by the recipe. |
Beta Was this translation helpful? Give feedback.
-
There are 5 different versions of the "output". When reading the recipe in from a DAT file, the software will try to read them in this order:
Show below is the configuration when reading |
Beta Was this translation helpful? Give feedback.
-
See above for the configuration when reading |
Beta Was this translation helpful? Give feedback.
-
Configuration when reading |
Beta Was this translation helpful? Give feedback.
-
The documentation for the I/O sequence is as follows: Essentially the code is as follows:
|
Beta Was this translation helpful? Give feedback.
-
The variant binary format is discussed in this thread: |
Beta Was this translation helpful? Give feedback.
-
This discussion thread is meant to document the recipe content. The recipe is saved as part of the DAT file.
Within the DAT header is a 64-bit big endian signed integer at byte offset 1000 for an attribute called
FileLength
. This value indicates the end of the image data and also where additional recipe information may be stored.FileLength
differs from the actual length of the file.Besides being saved in binary format at the end of the DAT file, the recipe information may also be saved as a CSV file.
Beta Was this translation helpful? Give feedback.
All reactions