James Fellows Yates
02/20/2024, 6:14 AMsys.getenv("PARAMETER") to call it within the config
We should decide on one way to make sure the advice is consistent, because people might get confused when getting conflicting info during reviews...
While I recognise 1 is more convenient, I prefer 2 as it reduces chances of getting the 'unrecognised parameter' warning as the parameter is not in the pipeline defaults.
I know you can add to parameter to ignore parameters validation, but I think it makes it slightly less portable because if a user move to a new cluster, they will think the parameter will work there. Whereas the bash variable is more likely to be considered specific to that HPC etc.
On the flip side, the potential change to configs may (?) Make the getenv system to not work, so might not work in the long run...
Can have a discussion in a thread on this post , but if you have a strong opinion can vote out right with emojis for option 1️⃣ and option 2️⃣mashehu
02/20/2024, 6:21 AMJames Fellows Yates
02/20/2024, 7:39 AMmashehu
02/20/2024, 7:40 AMJames Fellows Yates
02/20/2024, 7:40 AMJames Fellows Yates
02/20/2024, 7:40 AMmashehu
02/20/2024, 7:41 AMJames Fellows Yates
02/20/2024, 7:42 AMJames Fellows Yates
02/20/2024, 7:42 AMpontus
02/20/2024, 9:17 PMcheck_max in user configs all over.
But I don't think this is a big problem now, nor if someone needs to check the documentation when moving to a new cluster.
If it has been an issue for review (?), maybe it needs to be clarified that either is okay (along with an recommendation to follow what appears most natural for the resource)?