Script to back-populate existing projects for SNR and AcqOrderPerModality: Redmine 11284

[MounaSafiHarab]

• This is a script to be run once by existing projects upgrading to 17.0. This is in reference to these two pull requests (PRs):
  SNR computation #142
  and
  Order the acquisitions per modality based on series number: Redmine 10959 #160
• It should be run after you have applied the release patch -specifically containing table updates from PR: Imaging Preprocessing: Order the acquisitions per modality based on series number: Redmine 10959  Loris#2221 and upgraded your prod file as in this PR: Added the getSNRModalities function dicom-archive-tools#37
• Existing projects can now run this script (in the tools directory) to back-populate their existing database with SNR (in parameter_file table) and AcqOrderPerModality (in files) table.
• Run as follows in the /data/$PROJ/bin/mri/ directory:

tools/BackPopulateSNRAndAcquisitionOrder.pl -profile prod -tarchive_id 59 (for only this specific tarchive with tarchive_id = 59 in this example)

OR

tools/BackPopulateSNRAndAcquisitionOrder.pl -profile prod (for all tarchives in the tarchive table)

[cmadjar]

I get a Can't locate object method "orderModalitiesByAcq" error message. Maybe you need to rebase the branch with the latest aces/17.0-dev branch?

[MounaSafiHarab]

@cmadjar

yes, in the conversation I say it was awaiting #160 to be merged.
do you want me to rebase this pull request?

[MounaSafiHarab]

@cmadjar
I did rebase (I think and hope I did!); let me know otherwise!

[cmadjar]

Great! Thanks!!

[gluneau]

Please check so that if SNR function does not return anything, don't insert.

[MounaSafiHarab]

@gluneau
I will look into this, thanks Greg.
Thanks for bringing this up as well (this is to be used AFTER this has been merged:
#153) to avoid the msql errors on duplicate

[MounaSafiHarab]

@gluneau

done!
the latest commit here:
697df08
takes care of your comment (if $SNR ne ' ' ... only then do we setParameter)

[christinerogers]

Add context to the top line of this Pull Request blurb at top - e.g.
This is a script to be run by existing projects upgrading to 17.0.
It should be run after you have applied the release patch -specifically containing table updates from PRs ____ and ___ ...
@MounaSafiHarab

[MounaSafiHarab]

@christinerogers

your comment was taken into account and the conversation updated at the top of this pull request.