Version 5 (modified by 11 years ago) ( diff ) | ,
---|
New Minutes
Tags for blog posts
- Tag your blog posts so we can review them and decide how to incorporate them into the wiki
- To do this, in the Categories section of new blog post, add 'documentation'
How to keep track of documentation ideas
- Blog post tags
- A discussion/forum?
- Keep a documentation ticket up?
- Use the Czarships page to add to Wanted Pages drop down?
Wanted Pages
- Someone to fix plugin to list pages that are linked to but do not exist?
Changes to structure of wiki
- ideas?
Wanted Pages/page updates (taken from ticket 343)
- Update calculating run-times (page)
- use Eddie's calculations from Kraken
- relation between dt and dx we derived on blackboard
- when one does memory estimate the long way — this value should match the size of the output file (the chombo), and be off by ~10x the number reported in standard out — as the global info allocations reported there include both physical and ghost cells whereas memory estimates done the way we outline in wiki count physical cells only.
- Information on different clusters
- Do we have a page for this, where is it/where should it be?
- Bluestreak: helpful commands, how to submit jobs to reserved queue, memory/job limits
- Kraken: same
- Queuing system tips- for instance - BS doesn't consider the wall-time of currently running jobs, nor the requested wall-time for other queued jobs. Only queue up jobs in the order they are submitted. That is, they will wait till the resources are available for job 1 to start, rather than look at job 2 if it can run immediately with given resources.
- Emails back and forth with helpful information from CIRC to go up on wiki
- Number of nodes/memory per node in different queues, e.g. Afrank queue on BH. Max memory can request.
- Hypre partition, how/why it can fail on many processors
- Different types of memory - i.e. stack, virtual, and the amount you need to run your simulation, and the kinds of errors you might see if you hit this limit
- Organize the things you can do with problem module init
- i.e. the various pages on objects, etc.
- where are these pages located and where should the be located
- what new information do we want for problem module init
- Forking the wiki
- Page for Astrobear's capabilities
- maybe on front page?
- to resemble- this
- Running Visit in parallel
- How to add time-slider in physical units to Visit
- Update page on how to make column density maps
- FAQ page for new users
- do we want to get rid of the forums/discussion boards ?
- e.g. "problems related with restarts in MHD jets"
- where should this be? main page?
- Developer guide
- we should go through the guide as a group in future meetings to identify what needs improvement
- New user's guid
- we talked about possibly putting together a 1 page 'quick start' guide for New Users
Assignments/due dates
- (calendar plug-in ideas?)
Task | Assigned | Due-date |
Upcoming meeting topics
- New users guide
- Advanced users guide
Homework
- We should go through our old blog posts and tag them for documentation
- We should tags once pages are created
Note:
See TracWiki
for help on using the wiki.