Question: How are template files interpretted?
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 184
- Forks
- 53
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 1
Description
I've looked around in the docs and haven't been able to figure out how this works.
I'm working with the SGE template which appears to have three "levels" of code/text to be parsed by brew:
## text like this: comments
#$ -text like this: arguments to qsub
bare text like this: shell commands
When and where do the #$ lines get passed on to qsub (if that is indeed what happens)? Thanks for any help wrapping my mind around this!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the repository for the SGE template and qsub references. Trace where lines beginning #$ are handled and document when they reach qsub; done when the behavior is explained with a small confirming example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- hpc
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100