ct-sample-data.txt

vers 15 Feb 2024
started 15 Feb 2024

To go with...
http://wywtk.com/fea/sci/bio/ct/chal/ct-scans.htm

Only what is BELOW the line of equals signs would be in one of the data files.

The object of setting this data file format spec is not to tie your hands... but to make it easy for multiple people to work together, perhaps across the internet without ever meeting, to solve all the parts of the challenge. Please do write, if you feel the spec is flawed.

DESCRIPTION OF FILE CONTENTS...

First- A header section

1: <first line to start with ct-scans-challenge-data-set>
2: <next line to start "vers", and that to be followed by some sort of Version ID for the file>
3: <next two lines: Free form, to be filled with how to contact creator of data file>
4:<second of contact info>
5: <a simple integer, expressed as ASCII characters, indicating how many "views" were taken of the objects scanned. E.g. this line would hold "36" if the platter were rotated 10 degrees between images.>
6: <a simple integer indicating how many readings have been recorded across each image of the objects on the platter.>
7: <a simple integer indicating the angle of the view, in tenths of degree. I.e. if the view was 22.5 degrees wide, this line would hold 225.
8: (optional) the first of as many lines as you like with additional comments... but all such must start with a semi-colon#

Second- The data...

If, say, only 10 images were taken during one full rotation of the platter, then there should be ten lines here.

Each line should consist of a number of RGB data, with each line having the same number of data. If only a very crude CT scan was wanted, and only 8 data points were sampled in the looked-at row in the image, then there would be 8 RGB values on the line. They should be separated by commas. Wasteful? In disck space, yes... but it may save people tearing their hair, if they have to look at the data "by hand". Note that there is to be a comma at the end of each line, as well.

Each RGB value to consist of 2 ASCII characters from [0-9,a-f]. The first two being the amount of red, the second two the blue, the third the green... expressed in hexadecimal. (00-ff)

So... a very red pixel would be RGB ff0000.

After the last line of RGB values, there should be one final line. It should be "end of file", written out like that.

- - - -
So... a possible data file...


=============
ct-scans-challenge-data-set (sample from web-page)
vers 23c15-1700 (version of 15 Dec, 2023, 17:00)
Data created by TKBoyd. (Note it is meaningless. See below)
ng9apr665@sheepdogguides.com
5 (only 5 photos were taken- platter rotated 72 degrees between images)
10 (10 samples were taken across the row)
850 (the view subtended an angle of 85.0 degrees
;From here, every line until the data starts must begin with a semi-colon
;===
;Note: The data presented is MEANINGLESS. It will NOT
;   assemble into a sensible image.
;A typical file would have far fewer data with values of "000000"
;Next is first line of data...
000000,000000,12b500,000000,00ffff,000000,000000,000000,000000,000000,
000000,000000,08c900,000000,009b870000000,000000,000000,000000,000000,
000000,002500,000000,000000,000000,34b200,000000,000000,000000,000000,
000000,0032ca,000000,000000,000000,000000,000000,000000,000000,000000,
000000,000000,0000ff,000000,000000,000000,000000,000000,000000,000000,
end of file