Open joegati opened 4 days ago
Following up on this issue.
Protocol conversion from pre-existing parameter set in VE11C (N4) to XA60A appears to corrupt the acquisition. Re-building the protocol from scratch resolves the contrast and apparent fat saturation issue. Figure shows example of converted protocol, new build protocol (matched params) and equivalent SMS (matched params). Note that scan time is also different on 'converted' protocol compared to newly built - always by 4 seconds.
I guess the conversion process from VE11C to XA60 unexpectedly bypassed my logic to populate default values for new parameters. If you could send me a single DICOM file from one of the "bad" and "good" scans I could look to see in detail what (didn't) change.
For example, in this case my guess would be the new(ish) parameters for manually controlling the fat sat flip angle and frequency offset. In your "bad" protocol, maybe you can see if one of these parameters is off:
Thanks Eddie.Sent you DICOMs from the “converted” protocol and the equally matched “built” protocol in the email. Also a screen shot of the Fat Sat parameter settings in the Special tab from the converted protocol.
There wasn’t anything in the VE vs XA pulse sequence simulation that might indicate a problem either.
Cheers, Joe
Hello - We recently upgraded our Prisma (Fit) from VE11C to XA60A. There is a noticeable fat signal in MB acquisition (MB4) images with expected fat FOV shift. In Contrast Card the Fat-Water Contrast = "Fat Saturation". Setting to "Standard" - ie. no fatSat produces the same images. Building the equivalent with Siemens ep2d and SMS (=4) and Fat Saturation produces clean image with fat signal. Suggestions to remove? or is fatSat possibly broken for MB in XA60?