[Loris-dev] MINC insertion

[Cecile Madjar]

Hi Alfredo,

Could you point me to the version of the code you are using on GitHub so I
can take a look at the correct MRI.pm file.

Thank you!

Cécile

On Thu, Nov 25, 2021 at 8:09 PM Morales Pinzon, Alfredo <
AMORALESPINZON at bwh.harvard.edu> wrote:

> Hi Cécile,
>
> I’m getting the following error when inserting a minc file using the
> minc_insertion.pl script:
>
> ===
> $ perl minc_insertion.pl -profile prod -force -mincPath
> /data/BGI102001_207019_screening.mnc  -verbose -acquisition_protocol t1c
> -create_minc_pics
>
> DBD::mysql::db do failed: Cannot add or update a child row: a foreign key
> constraint fails (`IPMSA_LORIS`.`candidate`, CONSTRAINT `FK_candidate_1`
> FOREIGN KEY (`RegistrationCenterID`) REFERENCES `psc` (`CenterID`)) at
> /data_/ipmsa/loris_data/IPMSA/bin/mri/uploadNeuroDB/NeuroDB/MRI.pm line
> 1018.
>
> ERROR: Failed to insert record in table mri_scanner:
>
> The following database commands failed:
> PREPARE s FROM 'INSERT INTO mri_scanner
> (Serial_number,Software,Manufacturer,Model,CandID) VALUES (?,?,?,?,?)';
> SET @x1='syngo_MR_2004A_4VA25A', at x2='Siemens', at x3='Sonata', at x4='247660';
> EXECUTE s USING @x1, at x2, at x3, at x4, at x5;
>
> Error obtained:Cannot add or update a child row: a foreign key constraint
> fails (`IPMSA_LORIS`.`mri_scanner`, CONSTRAINT `FK_mri_scanner_1` FOREIGN
> KEY (`CandID`) REFERENCES `candidate` (`CandID`)) (error code 1452)
> ===
>
> Could you help me figuring out what is happening? Is there something I
> should add to the minc headers?
>
> Best,
> Alfredo.
>
> The information in this e-mail is intended only for the person to whom it
> is addressed. If you believe this e-mail was sent to you in error and the
> e-mail contains patient information, please contact the Mass General
> Brigham Compliance HelpLine at
> http://www.massgeneralbrigham.org/complianceline . If the e-mail was sent
> to you in error but does not contain patient information, please contact
> the sender and properly dispose of the e-mail.
>
> Please note that this e-mail is not secure (encrypted).  If you do not
> wish to continue communication over unencrypted e-mail, please notify the
> sender of this message immediately.  Continuing to send or respond to
> e-mail after receiving this message means you understand and accept this
> risk and wish to continue to communicate over unencrypted e-mail.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20211126/1f5f6daf/attachment-0001.html>