Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
mpsd-software-manager
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
MPSD Computational Science
mpsd-software-manager
Commits
4b22aa9a
Commit
4b22aa9a
authored
1 year ago
by
Hans Fangohr
Browse files
Options
Downloads
Patches
Plain Diff
add some questions raised this morning
parent
3872c14c
No related branches found
Branches containing commit
No related tags found
1 merge request
!76
Improve readme
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.rst
+52
-0
52 additions, 0 deletions
README.rst
with
52 additions
and
0 deletions
README.rst
+
52
−
0
View file @
4b22aa9a
...
...
@@ -196,4 +196,56 @@ Octopus) using the ``foss2022a-serial`` toolchain.
Frequently asked questions
--------------------------
- Can I install the ``mpsd-software-manager`` package in a python virtual environment?
Yes. ``pipx`` is probably more convenient, but you can create your own Pyton
virtual environment and install the ``mpsd-software-manager`` in that as a
regular python package::
python3 -m venv venv
. venv/bin/activate
pip install git+https://gitlab.gwdg.de/mpsd-cs/mpsd-software-manager
You just need to activate that python virtual environment before being able to
use the tool.
- Does the command write anything outside the mpsd-software-root directory?
No. All changes to disk take place in and below the mpsd-software-root
directory (which is the one in which the ``mpsd-software`` command is called).
- How can I uninstall the mpsd-software?
For now, the easiest is to delete the ``mpsd-software-root`` directory. You
can probably delete just a release subdirectory (such as ``dev-23a``) if you
have multiple release subdirectories installed and you only want to delete
one. (Untested.)
- How long does the compilation take?
This depends on the hardware. A few hours are typical per toolchain. If a
second toolchain is compiled in the same MPSD software instance is likely to
be faster, in particular if the same compiler is used (and thus the compiler
does not need to be re-compiled for the second toolchain).
- How much disk storage do I need?
A toolchain needs of the order of 5GB on disk. The second or third toolchain
(in the same MPSD software instance) will use less additional space, as
libraries and tools are re-used where possible.
- Can I have more than one MPSD software instance?
Yes.
We call "MPSD software instance" all the compiled software that is stored
in and below a "mpsd-software-root" directory (see instructions above).
It is possible to install multiple MPSD software instances on the same
computer (just in different (not nested) directories. This makes it possible
to experiment with toolchains etc.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment