-
Notifications
You must be signed in to change notification settings - Fork 13
Release 1.8.0 #816
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.8.0 #816
Conversation
The major problem was that xASL_adm_LoadParms just dumps all fields of the JSON into the x struct. This is not really helpful and maybe we should do this in a more controlled way in a future release. For now it should mostly be fixed. We use a standardized script called xASL_io_CheckDeprecatedFieldsX for this now. We use the same script for xASL_io_ReadDataPar and we could also integrate it in the LoadX function, we just have to use OldX.x for x there I think.
… table generation A single missing backslash t or missing comma within a TSV or CSV file should not break the pipeline before writing the results to a mat file
I encountered some bugs where the TSV reading did not work if we use xASL_tsvWrite with empty strings within the cell array. We should probably fix it there as well. For know, I fixed this in xASL_stat_PrintStat and xASL_stat_GetDICOMStatistics. I think the multiple subjects/sessions should work now, too. I will run the ten test datasets and then we can see if everything is correct now.
I am a bit surprised how this did work before. For me this breaks the code. It is not possible to assign a character array to a field of a numeric array. This would work for cell array though.
Test results from before 084349b, 86591ae & 14913c3Everything fine here... |
|
@HenkMutsaerts: let's discuss this here, because whatsapp isn't really that good for this kind of stuff 084349b and 14913c3 are okay, but 86591ae definitely isn't. I'm just saying that we should change... ...back to... I can't use the windows machine to test everything again today and I'm not in the office tomorrow, but somebody can test everything on linux and then it should basically be fine, because we had multiple testing rounds already. Agree @jan-petr & @HenkMutsaerts ? Edit: The optimal solution IMHO would be to use the check FSL script before quant BASIL and then skip this part. This could be a nice follow-up issue for 1.9.0. I don't care that much about all of this, it was just super non-transparent before and hard for me to find out what was going wrong without checking each and every log file (if you don't have FSL installed). |
But I don't want to have an arbitrary warning (folder exists already) at this point. I want to warn the user that this specific BIDS subject exists already. There's a difference there. AND I know you want to do this in more detail and discuss it and so on, but it is helpful to have it in 1.8.0 and it was tested a lot. That's just not moving in the right direction and I don't have time for this kind of stuff. Edit: Just realized that this doesn't really work as intended for multi-subject, multi-session datasets. I added a fix below. This way we know where to start for the next release and this helps with debugging. |
Henk asked for this a while ago, since we have to think this through. The previous version did obviously not work for multi-subject multi-session datasets. I removed the return statement and added another print statement. Please verify that my changes do not break anything.
|
One more try during the day ;) Philips_2DEPI_FLAIR_DisabledQuantification_M0_LoQYes, the problem was probably that the quantification wasn't skipped. If we skip it, we obtain similar numbers. Managed to reproduce the old 1.7.0 with 1.8.0. We are thus fine with the 2-fold increase in CBF. The other two are probably also fine - one was caused by the M0Processing and the other by the other parameters. But I guess we can fix the values now. But we should then save the 1.8.0 values as reference for both Windows and Linux. |
Sounds good. How do we handle the BASIL dataset? Edit: discussed, should be fine |
Windows test datasetsIt seems that my changes for the BASIL quantification now crash the pipeline at a later point if you don't have FSL/BASIL installed. I'd be more interested if all of this works nicely on a system with FSL/BASIL though. @jan-petr & @HenkMutsaerts: does this need fixing? Philips_2DEPI_Lesion_NoFLAIR_NoM0_HiQPhilips_3DGRASE_FLAIR_M0_2ndRun_HiQWindows flavor testsConversionThe BIDS conversion never worked that good before 😉 Processing
|
|
|
@MichaelStritt Yes, it definitively needs to be fixed. For once, it always does the normal quantification as well, even if BASIL is not installed, so it should never crash and always deliver results. |
|
I get this error, any ideas? |
|
Testing on macOS, with Jan, on Friday-eve trying to find out what is going on... Someone decided to use Matlab's built in
|
The first one is an issue, the second one is this PR right here that you're commenting in.
I thought the conclusion was that this wouldn't work for a commercial version. |
|
This has nothing to do with ... the fallback function for older versions I don't think the bids comparison function is the problem here though, I think our code tries to move an M0 that's not there. I guess something with the TopUp dataset doesn't work correctly in the import? Those are work in progress as far as I know, but please correct me if I'm wrong here @jan-petr & @HenkMutsaerts 👍 |
Flavor testingPhilips_PCASL_3DGRASE_5.1.7.2_1Philips_PCASL_3DGRASE_5.4.0.2_1 |
|
` Linux Matlab2019b |
BIDS conversionHere everything seems to work fine... |



Linked issue
Release PR, related issue #805.
How to test
Check out testing descriptions in #805.
Comments
Starting to test now, discussion (& release) on monday (if possible).