Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add / expand help / Q&A for using NCI OOD? #51

Open
Thomas-Moore-Creative opened this issue Mar 10, 2022 · 3 comments
Open

Add / expand help / Q&A for using NCI OOD? #51

Thomas-Moore-Creative opened this issue Mar 10, 2022 · 3 comments
Assignees

Comments

@Thomas-Moore-Creative
Copy link

Thomas-Moore-Creative commented Mar 10, 2022

Is it appropriate / useful to document platform specific Q&A in the guide?

Is this in scope & helpful?

If so how best to build an Q&A for NCI OOD as individuals hit issues and find solutions? Do we dump into the top platform page in the tree or make sub-pages for platforms?

@Thomas-Moore-Creative Thomas-Moore-Creative self-assigned this Mar 10, 2022
@hot007
Copy link
Contributor

hot007 commented Mar 10, 2022

Suggest breaking that platforms page up - make the top level a sort of index page listing the platforms, and move the content for each into sub-pages (though maybe put OOD and Gadi on the same page as one NCI page?). Then add an FAQ section to that page? I'm very happy to contribute to FAQs, I was on the receiving end of NCI help emails for the old VDI for the longest time and I think not that much has changed with the OOD :)

@hot007
Copy link
Contributor

hot007 commented May 12, 2022

hi @Thomas-Moore-Creative , I broke the content up, but in looking at the OOD FAQs it looks like most of them are covered already, though another thing has come up on the ARCCSS slack that I'll add, plus addressing the fixes @paigem identified. Could you please review the platforms area and particularly the OOD page and make any changes you'd like, once #62 is merged? thanks!

@hot007
Copy link
Contributor

hot007 commented Nov 24, 2022

I think we can close this as I believe this issue has been addressed.

However, I have not documented the fact that the Jupyter launch info indicates you give a path to a conda env, but in practise you need to give the full path to source python. I am happy to add this "gotcha" as it comes up a lot, but it's so ubiquitous I assume it's surely just a matter of time till NCI fix their instructions!? The OOD is fine but the ARE info is misleading.
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants