add quast rule

[bgruening]

xref: usegalaxy-eu/infrastructure-playbook#1791

[cat-bro]

We have this for quast on AU and it’s mostly OK:

    cores: 16
    mem: 62
    rules:
    - id: quast_small_input_rule
      if: input_size < 0.01
      cores: 2
      mem: 10
    - id: quast_medium_input_rule
      if: 0.01 <= input_size < 1
      cores: 4
      mem: 16

Every now and then there is an OOM for the 62GB case. I have looked into parameters used for these OOM jobs and often either use_ref or large is not set to true, so these jobs would only be getting 12GB under this new scheme.

AU unfortunately cannot run quast with more than 100GB or so*, so if this is merged I’ll put in a rule in AU’s config to override this one and give the big jobs 100 instead.

*quast cannot run on pulsar because the icarus link from the html does not work. I haven’t figured out whether it’s pulsar or the wrapper at fault in this case.

[bgruening]

If you like we combine your rules with the proposed here. You would still.need to overwrite it until the pulsar issues is figured out.

[bgruening]

@cat-bro how do you want to proceed here?

[cat-bro]

If this is working for you, we could merge it as is? I can add an override for AU because 250 is too much for quast-friendly destinations. This could be good for AU and prevent us from overspending resources on quast jobs.