Is there a fix for reading GE P-files version 23x

We just installed 23.1 and the tools still work for us. I don't think
the headers changed much -- only some unused fields were populated. In
fact the version number on our P-files still indicates "20" even though
they were generated on a 23.1 system (same thing happened on 22x). If
you have Pfiles that don't work, let me know.

yes one P-file 1.7GB using the product epiRT

the output is a bxh file with 4.6K instead of a 1.4MB file using the DICOM files

command i am using is
pfile2xcede --xcede2 P46080.7 output.bxh

A .bxh (or XCEDE) file is only a wrapper to data in other files. So the
wrapper in the DICOM case is going to be a lot larger because in the GE
case it is pointing to many (sometimes thousands) of DICOM files.

In the pfile2bxh case, it only parses the P-file header for the image
metadata, not the actual image data. If you want to give it image data
to wrap too, you need to specify it as a separate input file:

pfile2bxh PFILE IMAGEDATA.raw WRAPPER.bxh

The P-file generally contains k-space data, not reconstructed image
data. For our in-house pulse sequences, we recon the k-space data from
the P-file into a raw image data file and then use the above command to
get them all wrapped together by the same .bxh file. For sequences that
generate DICOM, we just use the DICOM (though there are a few fields in
the Pfile header that we wish were in the DICOM, so we might soon take
advantage of both and merge them).

If I am misunderstanding your problem, please let me know!

Thank you Syam

understand that no problem, i have been using these tools for a few years now and

what happened i could process the resulting bxh file from the DICOM but the one from the bxh
with fmriqa_phantomqa.pl

but i get the error below

XYZtoRAS = ( 0,1,2 )
Segmentation fault (core dumped)
Error running bxh2analyze

Sorry, then I did misunderstand the problem. Could you attach the
resulting XML file and I can take a look? (check to make sure there is
no subject identifying information)

Thank you for looking at it Syam

it's from a phantom

Thanks.

The XML file does not point to any actual image data.  Did you specify a raw data file on the command line?  Can you provide the actual command line you used?

pfile2xcede --xcede2 P46080.7 output.bxh

Right, so in our experience, P-files don't have any reconstructed image data in them, only k-space data. pfile2bxh is grabbing the metadata (dimensions, orientation, voxel spacing, etc.) but if you want it to attach that to image data you need to also specify a raw image data file containing the output of the reconstruction, like in the commands I mentioned previously. If you only specify the P-file to pfile2bxh, then it will just be a wrapper around an empty dataset. If this is a stock epiRT scan, I'd recommend just using the DICOMs, which contain the reconstructed image data.

pfile2bxh --xcede2 P46080.7 output.bxh

many thanks, sounds good

I thought i would be able to use the pfile