Sync a bit further

Nice, but it is only a small step further to make this function really multi- and single-PLD ignorant as much as possible, and only at the end do a check for dependencies.

Agree with this philosophy in general. And parts of the code should be like that. If not, please make specific comments or propose new issues. I would prefer to do only the basics here.
For example, we should make a new issue that multi-TE single-PLD are correctly crunched - lets do that with the newly added flavor that you have.

This will help with the generalizability, and readability of our code. In many instances, you want the same for multi-PLD and single-PLD, or it is something that won't matter for single-PLD (like sorting or choosing which PLD or LabDur to use).
Here - the sorting will differ a bit necessarily. Not that it would have to be done differently in principle, but the implementation of the sorting for single and multi-PLD will slightly differ, so we need to account for it.

A dependency could be: warning: multiple PLDs detected but singlePLD quantification requested, using max PLD instead, this may give suboptimal results
There's never a mutli-PLD detected, but single-PLD requested - we don't have an input option for that. We can open a new issue and create such an option.

and later, we could replace this by:
warning: multiple PLDs detected but singlePLD quantification requested, using multiPLD quantification instead
OR
warning: multiple PLDs detected but singlePLD quantification requested, now performing both using multiPLD and singlePLD quantifications

Yes - but see above.

Only quantification

Also, you didn't do the second requirement in the issue list, you only merged the quantification right? I changed the title of the issue & PR accordingly, and we can make a new issue for merging this in other locations (or do we really not have multi-PLD specific processing elsewhere yet? Then we should make that a new issue, if we don't have it already ;) Anyway, in that case the title change would still be good, but my comment can otherwise be ignored

Yes - I only merged stuff.

Please pull

I did a small spelling correction & layout for readability, and I didn't want to annoy you by asking this so I did it myself :)

Perfect - that makes things more efficient. And I anyway check all new commits for errors.

Reviewers

Bea doesn't need to review this right?

Review code itself not, but test yes :D Hence the review request.

Looks good, I did a minor revamp of xASL_quant_ASL

Looks all good. But Bea still needs to run it and test on both single/multi-PLD and Hadamard.

All good after testing TestDataSets