On 11/03/2017 06:21 PM, Roland Haas wrote:
Hello Steve,

thank you very much for providing this. This is great!

Please send comments, flames, etc. Thanks.
Comments:
* in the list of stuff to install, it should also cover OSX (homebrew
   and macports). Win10 would be nice but is maybe tricky.
Someone will have to help me with mac. As for Win10, if you use
the subsystem it should be the same as ubuntu.
* how would plotting work inside of the container?
I assume you mean if you run command line rather than as a notebook. There are a couple of ways to do this. Maybe the easiest way would be to enable ssh inside the container and rather than giving a bash prompt, allow people to log in with ssh -X.
* those install commands are not needed in the container or in the nds
   machine are they? This should likely be stated.
They are not.
* how to install "which" is only described after the user is asked to
   run "which mpirun". This should be changed.
OK
* do you sometimes need to explicitly ask for perl?
It seems not.
* it may be good to sort the list of packages alphabetically to make it
   easier (for us) to add / remove packages from the list
That is easy to do since the list is generated from a script.
* I think GetComponents --parallell has a bug right now:
https://trac.einsteintoolkit.org/ticket/2060 which did not (yet) make it into 
the release branch
Regardless, it works on the NDS machine.
* it maybe good to explain what "%" and "!" do in a jupyter script. How
   would these commands look like if someone chose to take us up on the
   offer to get a shell?
Yup.
* the build command used "make -j5" but the text above claims it uses
   "-j2"
Noted.

--Steve
Flames:
* none
Thanks:
* many

Yours,
Roland



_______________________________________________
Users mailing list
[email protected]
http://lists.einsteintoolkit.org/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.einsteintoolkit.org/mailman/listinfo/users

Reply via email to