Maneage - Tasks: task #15361, Tips, guide-lines, FAQs
You are not allowed to post comments on this tracker with your current authentication level.
task #15361: Tips, guide-lines, FAQs
Submitter: | Boud Roukema <boud> | ||
Submitted: | Wed 07 Aug 2019 09:40:18 PM UTC | ||
Should Start On: | Wed 07 Aug 2019 12:00:00 AM UTC | Should be Finished on: | Wed 07 Aug 2019 12:00:00 AM UTC |
Category: | None | Priority: | 1 - Later |
Status: | None | Privacy: | Public |
Percent Complete: | 0% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
Thu 08 Aug 2019 12:56:30 AM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi>![]() |
Wed 07 Aug 2019 09:40:18 PM UTC, original submission:
Quoting https://www.open-mpi.org/doc/v2.0/man1/mpirun.1.php#sect22
|
Boud Roukema <boud>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follows 1 latest change.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-08-08 | makhlaghi | Summary | mpi FAQ - openmpi refuses to run as root | ![]() |
Tips, guide-lines, FAQs |
This is a good point! Once we make a webpage/documentation we should add a "Tips" or "Guidelines" section which can be very useful for beginners.
Many people are SUPER-interested in properly organizing their research analysis steps using something like this template. But they need guidance/tips on how to effectively do so. Afterall, as natural scientists, we are not well trained in software egineering tools: many don't even know Git (but fall in love it once they learn it!).
Because of this, even at this early stage, based on my experience with new adopters of this template, I felt that its necessary to add a Tips for designing your project in the `README-hacking.md.
So indeed, I feel we really need to add a section with useful tips on using various software reproducibly.
Since the discussion seemed to be more about adding documentation with tips/FAQs for using software reproducibly, I changed the tile of this task.
Let's use this task to share any tips we find based on experience (like the one you just reported). This way, we won't loose the good points until that a special page is setup for this job.