Checking for non-preferred file/folder path names (may take a long time depending on the number of files/folders) ...
This resource contains some files/folders that have non-preferred characters in their name. Show non-conforming files/folders.
This resource contains content types with files that need to be updated to match with metadata changes. Show content type files that need updating.
|This resource does not have an owner who is an active HydroShare user. Contact CUAHSI (firstname.lastname@example.org) for information on this resource.
|The size of this resource is 119.6 MB
|Jan 18, 2022 at 12:38 a.m.
|Feb 15, 2022 at 8:22 p.m.
|See how to cite this resource
|Be the first one to this.
|No comments (yet)
Illustration of General idea of use case for sciunit container.
1. User creates sciunit (sciunit create Project1)
2. User initiates interactive capturing (sciunit exec -i)
3. User does their work. For now assume this is a series of shell commands
4. User saves or copies the sciunit
5. User opens the sciunit on a new computer and can re-execute the commands exactly as they would have on the old computer, from command line, from bash shell escapes or python in Jupyter
6. User sees a list of the commands that were in the sciunit and could use editing of them to reproduce
On CUAHSI JupyterHub the user has a resource (the one above) with some code that is a simple example for modeling the relationship between streamflow and snow
There is a python "dependency" GetDatafunctions.py in a folder on CUAHSI JupyterHub. This is not part of the directory where the user is working. It is added to the python path for the programs to execute. This is a simple example of what could be a dependency the user may not exactly be aware of (e.g. if it is part of the CUAHSI JupyterHub platform, but not part of other platforms).
An export PYTHONPATH command is used to add the dependency to the python path.
Then the analysis is illustrated outside of sciunit.
Then sciunit is installed and the analysis repeated using sciunit exec.
Finally sciunit copy copies the sciunit to the sciunit repository
Then on a new computer
Sciunit open retrieves the sciunit
After repeating one of the executions, the sciunit directory has the dependency container unpacked
Setting the PYTHONPATH to the unpacked dependency allows the commands to be run on the new computer, just as they were on the old computer.
This is the vision - running on the new computer with dependencies from the old computer resolved.
Would like the dependencies to be “installed” on the new computer so that they work with Jupyter and Jupyter escape bash commands.
All is done from the command line - the Jupyter Notebook is just used as a convenient notepad.
How to Cite
This resource is shared under the Creative Commons Attribution CC BY.http://creativecommons.org/licenses/by/4.0/