LSF scheduler seems to have redundant memory keyword
Open
LSF
- Dominant language
- Python
- Stars
- 256
- Forks
- 150
- PR merge metrics
- No merged PRs in 30d
Description
It looks like specifying the lsf scheduler requires two memory keywords (mem, and memory). Should mem on the LSF scheduler be turned into memory so that it lines up with other schedulers and the core object?
Contributor guide
Assessment
This issue has not been assessed yet.