You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Examples and Tutorials section of the documentation re-creates the outline of the notebook tutorials, which are rendered on the same page as the documentation. Instead, this section should just link to the Fornax Tutorials section.
There needs to be some indication of how to connect these tutorials to the Fornax Science Console. For example, if I want to use the Forced Photometry notebook in the Fornax Science Console, do I just need to download the tutorial from github and then upload it into the Console? And which files do I need?
The text was updated successfully, but these errors were encountered:
ok, so now we need documentation on how to use the cloned repo that shows up in /opt/notebooks. questions I just sent to the helpdesk include:
How do we actually see those notebooks? I can’t figure out how to get them to show up in the left file folder listing, and therefore can’t open them as notebooks.
Will users be able to overwrite these files or are they read only? What is the best practice for users to play with these notebooks? ie., should we suggest copying them to a different directory, or cloning them again if a user wants to open a branch and make some changes?
Currently the Examples and Tutorials section of the documentation re-creates the outline of the notebook tutorials, which are rendered on the same page as the documentation. Instead, this section should just link to the Fornax Tutorials section.
There needs to be some indication of how to connect these tutorials to the Fornax Science Console. For example, if I want to use the Forced Photometry notebook in the Fornax Science Console, do I just need to download the tutorial from github and then upload it into the Console? And which files do I need?
The text was updated successfully, but these errors were encountered: