Changes for page Documentation Lab

Last modified by mmorgan on 2023/05/11 11:30
From version 9.1
edited by chaney08
on 2021/07/20 20:18
Change comment: There is no comment for this version
To version 3.1
edited by chaney08
on 2021/05/27 11:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -Collabs.the-collaboratory.WebHome
1 +Collabs.collab-devs.WebHome
Content
... ... @@ -1,15 +1,9 @@
1 1  == Collaboratory.Lab ==
2 2  
3 -The Lab gives EBRAINS users the ability to develop and run programs in the cloud from their web browser, without needing to install anything on their local machine. The Lab offers a readily installed programming environment and **all of the EBRAINS tools** and libraries which can be run from it. These programs will be run on the EBRAINS servers. The Lab gives users a JupyterLab user interface manage, edit and run their Jupyter Notebooks. A notebook is a programming environment which includes code (typically in Python), text for documentation purposes, and which stores the output of the previous execution of the code.
4 4  
5 -Users can access the Lab from the //Lab //navigation element in every collab that they are a member of (not from a public collab if they are not a member of its team).  Once in the Lab, users see all of the files in the Drive of the corresponding collab (including the notebook files with the ***.ipynb** extension which can be opened in JupyterLab) and can navigate to the Drive of other collabs. More instructions can be found in the [[Tutorial section>>doc:.Tutorial.WebHome]].
4 +The Collaboratory.Lab gives users the ability to develop and run programs in a browser, without needing to install anything on their local machine, these programs will then be run on the EBRAINS servers. The Collaboratory.Lab works by providing users access to a JupyterLab service and create Notebooks, a Notebook is where you put your code and is what is executed when you press run.
6 6  
7 -=== Container and Kernel ===
8 8  
9 -In the Lab, a user runs a notebook in a container, i.e. an environment isolated from other notebook executions of other users. All the notebooks of a user on a given server run in the same container. So files produced by one notebook can be accessed from another notebook but only by the same user. The context of a container is lost (including files stored in the container) when the container is reset.
7 +You can access JupyterLab from the //Lab //menu at the top of this page. Double click the drive folder to find notebooks in the existing collabs, organized in 3 folders depending on Share permissions of each collab (see permissions below).
10 10  
11 -The Drive is mounted in the container as an additional partition (at /shared) and files in the Drive are not affected by container resets.
12 -
13 -The term "Kernel" in the Jupyter notebook environment indicates the language interpreter used for a given notebook. The Lab currently supports the Python 3 language and others may be added in the future.
14 -
15 -
9 +=== ===