-
Notifications
You must be signed in to change notification settings - Fork 13
Closed
Description
Description
For HAD8, the BasilOptions.txt has the PLD order like this "0.6, 0.8, 1, 1.2 , etc", instead of "0.6, 1, 1.4 .... 0.8, 1.2, 1.6 ..." as the order of the PWI4D nifti for HAD8.
Here, in the xASL_quant_FSL function, if we don't invert the index matrix we'll be fine:

NB: I was testing the sessions the other way around to be able to automatize the concatenation (ASL_1 = HAD8, ASL_2 = HAD4). I don't know if that might have influenced the bug...
Tasks Jan
- Fix PLD order in function
xASL_quant_FSL - Check Siemens_PCASL_3DGRASE_VD13A_DEBBIE_1
- Check Siemens_PCASL_3DGRASE_VE11C_DEBBIE_1
- Check Siemens_PCASL_3DGRASE_VE11C_DEBBIE_2
- Check Siemens_PCASL_3DGRASE_VE11E_DEBBIE_1
- Check Siemens_PCASL_3DGRASE_XA30_DEBBIE_1
Tasks Bea
- Check Siemens_PCASL_3DGRASE_VD13A_DEBBIE_1 --> running
-> 1 rep only for HAD8, but PLDs are fine + nifti PLDs order also fine
-> CBF map (HAD8):
->Tex map (concatenated): - Check Siemens_PCASL_3DGRASE_VE11C_DEBBIE_1 --> running
-> 2 reps for HAD8, but PLDs are fine + nifti PLDs order also fine - Check Siemens_PCASL_3DGRASE_VE11C_DEBBIE_2 --> runnning
- Check Siemens_PCASL_3DGRASE_VE11E_DEBBIE_1 --> running
- Check Siemens_PCASL_3DGRASE_XA30_DEBBIE_1 --> running
Release note
Minor fix in PLD ordering for FSL.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working