First-time user observations and error #28
Comments
|
Thanks for sharing this! One could indeed write a lot of information into log file instead of showing it.
It looks like you gave the same folder for the setup installation and the juliaup installation. If you change that then it should work. |
|
You can try with To avoid that people get worried because of the time nothing is happening a progress bar should be added... |
|
Note that at this point only the setup is installed. Juliaup and julia will be installed at first call of |
Okay, that indeed is a lot cleaner! Suggestion to move the log file to
Ah, indeed I messed that up. I also wasn't noticing that installation to $ |
|
@paulmelis : I think i have addressed all the issues you raised. Could you please try again using the branch from the PR setting version as before? I also added a key word argument for verbosity. All the changes are documented here: https://github.com/JuliaParallel/JUHPC/tree/initial?tab=readme-ov-file#2-call-juhpc |
|
Yep, seems all okay now! |
|
Great! Could you do a PR to include your configuration and testing in the examples: |
|
Sure, I can look into that. One thing I'm still not clear on is this point:
|
|
JUHPC_SETUP_INSTALLDIR is meant conceptually for all users or for a group of users (of course in practice it can also be for a single end user) |
No it will complain if any of the directories exist already |
Great! |
|
These statements seem to conflict?
versus
Can or can't JUHPC_SETUP_INSTALLDIR be used multiple times for different JULIAUP_INSTALLDIR's? |
No, the statements don't conflict. Only one HPC setup can be installed into a JUHPC_SETUP_INSTALLDIR, however, multiple users can use it and it should contain a JULIAUP_INSTALLDIR that expands differently for each user as explained here: https://github.com/JuliaParallel/JUHPC?tab=readme-ov-file#2-call-juhpc |
Then I must be missing information, as it seems |
|
@paulmelis I have merged the changes into main. You can now use |
|
@paulmelis Here is a use case that will hopefully clarify things for you. For a course, we need to use the old supercomputer, because the new one is currently not available for this purpose. The software stack of the old supercomputer is frozen because it is decommissioned very soon. Thus, I have created a Julia HPC setup using JUHPC specifically for this course. I have run Now all the students can activate the setup by executing (found in this file: The students never need to run Does this use case clarify things for you? |
|
@paulmelis I have released a new version, 0.3.0. Please use this one for your configuration PR! |
|
@paulmelis Please let me know if the above use case clarified things for you and what do you think could be added to the documentation to make it clearer. |
First up, great that someone's working on making Julia use on HPC systems easier!
As I'm now trying JUHPC for the first time here's some things I noticed/ran into. Background: viz guy at Dutch HPC site, so consider me an "internal user" of our system :)
First, there's a lot of output coming not just from JUHPC, but also some of the programs it calls itself. This is a bit confusing, as it's not immediately clear what to pay attention to and what can be ignored. Example below, apparently stuff gets installed in a tempdir, which resolves to
/dev/shmon our system, which is fairly non-standard, but okay. The thing I wasn't clear on was if "You can uninstall at any time with juliaup self uninstall and these changes will be reverted" was something I needed to remember or not. It's only at the end when it reads "cleaning up temporary juliaup installation in /dev/shm/paulm/juliaup" that I figured all the/dev/shmstuff was not relevant for the end result. Perhaps putting all that output in a log file would be better, as it hides unnecessary details that aren't of interest to the average user.For the lines below a similar thing applies, as I assume the "re-start Julia" instruction really is just a detail that isn't relevant for JUHPC installation.
After then trying to activate the installed JUHPC environment it seems the first steps are okay:
But not having a
juliaavailable is somewhat surprising:And
juliaupis where I would expect it, but running that gives me an error:The error doesn't make much sense to me, as I assumed juliaup was already installed earlier? Since the installation took quite a few minutes and processed a lot of Julia packages. So perhaps something is going wrong on my end?
So with respect to actually using (as an end-user) the installed JUHPC environment I'm unsure what to expect. For example, one of the example scripts in the repo here shows the line
. $JUHPC_SETUP_INSTALLDIR/activate, but I assume that I don't need to keep$JUHPC_SETUP_INSTALLDIRset, as that would defeat the purpose of having separate install directories?The text was updated successfully, but these errors were encountered: