[Loris-dev] question regarding visit labels
Ling Ma
lingyun.ma at mcin.ca
Thu Feb 20 11:13:35 EST 2020
2) or "does not match the requirement specified in the mri_protocol_checks"
On Thu, Feb 20, 2020 at 11:11 AM Ling Ma <lingyun.ma at mcin.ca> wrote:
> Hi Ioannis,
>
> 1) The Image Uploader's Visit labels are those already existed, populated
> from session table. While <visitLabel> session is used to create a
> visitLabel which you could use to generate a timepoints, then the
> visitLabel might be visible in image uploader.
> 2). The mri_protocol min, max specifications are not used to identify the
> violations, the violations could be flag only if the protocol is unknown.
>
> Best regards,
> Ling Ma
> Dev consultant
>
> On Wed, Feb 19, 2020 at 10:41 PM Ioannis Pappas <ioannis at berkeley.edu>
> wrote:
>
>> Hi Loris support.
>> I hope you are well. I m using Loris version 21.0.1. I have two questions
>> if you allow me. 1) First I am trying to manually define my visit labels
>> like this in project/config.xml
>>
>> <visitLabel subprojectID="1">
>> <generation>sequence</generation>
>> <regex>/^[A-Z0-9]{2}$/i</regex>
>> <length>2</length>
>> <suggest>V%value%</suggest>
>> <labelSet>
>> <item value="V1">V01</item>
>> <item value="V2">V02</item>
>> <item value="V3">V03</item>
>> </labelSet>
>> </visitLabel>
>>
>> which is very similar to the one you provide in the documentation
>>
>> <visitLabel subprojectID="1">
>> <generation>sequence</generation>
>> <regex>/^[A-Z0-9]{2}$/i</regex>
>> <length>2</length>
>> <suggest>V%value%</suggest> <!-- %value% will be substituted
>> for the next unique number -->
>> <labelSet>
>> <item value="V1">V1 label description</item>
>> <item value="V2">V2 label description</tem>
>> </labelSet>
>> </visitLabel>
>>
>> However when I am trying to experiment and upload a scan (e.g. via the
>> Imaging Uploader gui) the values don't show up in the dropdown box for the
>> visit labels. Am I doing something foolish and wrong?
>>
>> 2) From my understanding the uploaded scans will be automatically
>> identified (in terms of whether this is t1,t2,or flair for example) via the
>> min and max specifications in the mri_protocol table (that is further
>> connected to the mri_scan_type table). Is this correct? Subsequently any
>> violations will be defined based on these bounds.
>>
>> Best wishes,
>> Ioannis
>> _______________________________________________
>> Loris-dev mailing list
>> Loris-dev at bic.mni.mcgill.ca
>> https://mailman.bic.mni.mcgill.ca/mailman/listinfo/loris-dev
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.bic.mni.mcgill.ca/pipermail/loris-dev/attachments/20200220/fe7c763d/attachment.html>
More information about the Loris-dev
mailing list