Hi <@UV41DBFAT>, I seem to remember a PR or issue...
# modules
m
Hi @Edmund, I seem to remember a PR or issue in the modules repo with dynamic mem allocation for bwa. Could you point me towards there? I can’t seem to find it anymore 😞
✅ 1
Ah nevermind.. It was just applicable to
BWA_INDEX
m
bwamem2 also I believe
@Anders Sune Pedersen was asking questions about that earlier
a
Yeah, our HPC didn’t handle this new memory allocation so well.
For the test-profile of Sarek, the
memory { 6.B * fasta.size() }
was resolved to
Copy code
#PBS -l mem=238.3kb
in the
.<http://command.com|command.com>
m
Thats not good 😮
So it’s the dynamic resource stuff that doesn’t work
a
hm - not sure if it is a common problem.
I think it triggered
Copy code
Illegal attribute or resource value for Resource_List.mem
from the queueing system (PBS)
There is also this thing with our HPC that jobs seems to require at least X GB memory to start. (Don’t know the exact value of X - my colleague says 5GB)
m
Ah ok, so not a broken language feature
a
I solved it in that particular module with this :
Copy code
memory {
      def bytes = 6.B * (fasta?.size() ?: 0)
      def gb = Math.ceil(bytes.toGiga()) as long
      gb = Math.max(5L, gb)
      return "${gb} GB"
    }
e