<bavier[m]>I think for metis, many use REALTYPEWIDTH=64 as the default. I have not heard anyone complain about a meaningful difference in performance.
<rekado>civodul: reading the snakemake documentation always makes me sigh and grunt
<rekado>that’s probably why I avoid it and only hear of their features too late
<bavier[m]>civodul: and the scotch/scotch32 is to differentiate the integer type size, which is a bit different. I'm fine either way though.
<rekado>I really should work on this “guix workflow pack” thing
<rekado>I thought about it when I had just finished translating the pigx-rnaseq workflow and then noticed that the rnaseq process scripts were not statically determined (they depend on the pigx configuration file / sample sheet), so that made me defer work on this feature.
<rekado>for really simple, static workflows this is trivial to implement
<rekado>I’m guessing that the PiGx case is more common, and perhaps this means that some changes to GWL are necessary.
<civodul>i suppose "guix workflow pack" could boil down to creating a pack around the entry-point script, no?
<civodul>bavier[m]: perhaps we should change the default to REALTYPEWIDTH=64 then, and add a 32-bit variant?
<bavier[m]>civodul: yes. We should consider the naming carefully though, to not confuse users, since metis also has a 32/64-bit choice in index sizes.
<bavier[m]>changing the real width doesn't fit nicely into the "familiar" ilp64-type naming.
<rekado>civodul: my expectation for “guix workflow pack” is that Guix would not be required at runtime.
<rekado>but if the job scripts depend on user inputs, then we need Guix to compute them at runtime.
<rekado>that’s what I remember from my experiment with pigx-rnaseq
<rekado>I think it’s just a matter of finding the right “level” to shift the code to, but as it stands the pigx-rnaseq workflow creates *different* job scripts dependent on the contents of the configuration file
<rekado>just as I moved the values of inputs and outputs outside of the job scripts (they are now passed as arguments to the script instead of being embedded), I hope I can do the same for whatever causes these job scripts to be variable.