Discussion List Archives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Imgcif-l] CBF - Adding binary proprietary format header dump

Thanks to everyone for the input.

We have decided to register the "rayonix" category to hold our binary 
header.  There is information that we would like to save in our binary 
header which does not translate to ASCII but which would be useful for 
diagnostic purposes.  The marccd program suite does include a 
"dump_header" program which writes out most of the binary header data in 
text format but the results are not user friendly nor are they 
comprehensive.  The intent of writing our binary header to the CBF file 
is not to get around writing data to the CIF header but, rather, to 
include additional information which could be useful later.  The users 
will not need to read the binary header.

I am assuming we can use any subcategories we wish with the "rayonix" 
category.  We were thinking the header would reference the image array 
by giving it the same .array_id.  Since we are only writing one binary 
item then we assume the default .binary_id of "1" will suffice.  We will 
use CBFLib to write the binary header data so that it will have a MIME 
as well.

Regards,


Justin Anderson                    Rayonix, LLC (Formerly Mar USA)
Software Engineer                  justin@rayonix.com
1880 Oak Ave. Ste. 120             Evanston, IL, USA 60201
877.627.9729                       847.869.1548


On 09/25/2007 08:18 PM, Herbert J. Bernstein wrote:
> One important point -- while, strictly speaking, there should be no harm
> in adding additional binary sections anywhere in a CBF, I believe people
> have gotten used to finding the image as the first (and in all current
> cases as the only) binary section.  So, it might be a good idea to put
> such supplemental binary header binary sections after the image, so that
> packages that are looking for the image don't get confused.
> 
> Personally I would agree with Harry that an ascii translation of binary
> header would be easier to work with in checking the format.  That could
> appear before the image with the risk of confusion.
> 
> Regards,
>   Herbert
> =====================================================
>  Herbert J. Bernstein, Professor of Computer Science
>    Dowling College, Kramer Science Center, KSC 121
>         Idle Hour Blvd, Oakdale, NY, 11769
> 
>                  +1-631-244-3035
>                  yaya@dowling.edu
> =====================================================
> 
> On Mon, 24 Sep 2007, harry powell wrote:
> 
>> Hi
>>
>> I don't understand why you'd want to add the binary header, to be
>> honest. I can see why you might want to have the contents of the
>> header as an ASCII comment section - but I think this should just be
>> a check while developing the file format.
>>
>> Could you elaborate why you'd want it there?
>>
>>> Hello everyone,
>>>
>>> We here would, in fact, like to add our binary header to the CBF file.
>>> Should that just go into an additional binary section, with MIME
>>> header
>>> and all of that?  If so, is there any recommendation as to how we can
>>> refer to it in the CIF headers so that I can distinguish between the
>>> binary image data and our binary header data?  My inclination is to
>>> add
>>> the ".header_convention" column to my "_array_data" loop and fill
>>> it in
>>> with "RAY_1.0" or something like that for the our binary header and
>>> with
>>>   an empty value "" for the image data.
>>>
>>> e.g. :
>>>
>>> loop_
>>> _array_data.array_id
>>> _array_data.binary_id
>>> _array_data.header_convention
>>> _array_data.data
>>>   ARRAY1 1 RAY_1.0
>>> ;
>>> --CIF-BINARY-FORMAT-SECTION--
>>> <<MIME header for Rayonix binary header dump>>
>>> <<Rayonix binary header dump>>
>>> --CIF-BINARY-FORMAT-SECTION----
>>> ;
>>>   ARRAY2 2
>>> ;
>>> --CIF-BINARY-FORMAT-SECTION--
>>> <<MIME header for image binary data>>
>>> <<Image binary data>>
>>> --CIF-BINARY-FORMAT-SECTION----
>>> ;
>>>
>>>
>>>
>>>
>>> Regards,
>>>
>>> --
>>> Justin Anderson                    Rayonix, LLC (Formerly Mar USA)
>>> Software Engineer                  justin@rayonix.com
>>> 1880 Oak Ave. Ste. 120             Evanston, IL, USA 60201
>>> 877.627.9729                       847.869.1548
>>> _______________________________________________
>>> imgcif-l mailing list
>>> imgcif-l@iucr.org
>>> http://scripts.iucr.org/mailman/listinfo/imgcif-l
>> Harry
>> --
>> Dr Harry Powell, MRC Laboratory of Molecular Biology, MRC Centre,
>> Hills Road, Cambridge, CB2 2QH
>>
>>
>>
>>
>> _______________________________________________
>> imgcif-l mailing list
>> imgcif-l@iucr.org
>> http://scripts.iucr.org/mailman/listinfo/imgcif-l
>>
> _______________________________________________
> imgcif-l mailing list
> imgcif-l@iucr.org
> http://scripts.iucr.org/mailman/listinfo/imgcif-l
> 
> 
_______________________________________________
imgcif-l mailing list
imgcif-l@iucr.org
http://scripts.iucr.org/mailman/listinfo/imgcif-l

Reply to: [list | sender only]
International Union of Crystallography

Scientific Union Member of the International Science Council (admitted 1947). Member of CODATA, the ISC Committee on Data. Partner with UNESCO, the United Nations Educational, Scientific and Cultural Organization in the International Year of Crystallography 2014.

International Science Council Scientific Freedom Policy

The IUCr observes the basic policy of non-discrimination and affirms the right and freedom of scientists to associate in international scientific activity without regard to such factors as ethnic origin, religion, citizenship, language, political stance, gender, sex or age, in accordance with the Statutes of the International Council for Science.

Useful links