RAVEN is a flexible and multi-purpose probabilistic risk analysis, validation and uncertainty quantification, parameter optimization, model reduction and data knowledge-discovering framework.
It would be useful to be able to add to the mamba creating command line, because sometimes this is needed to get it to work.
For example, #2197 was caused by the following error
Could not solve for environment specs
The following packages are incompatible
├─ python 3.8** is requested and can be installed;
└─ truststore is not installable because there are no viable options
├─ truststore [0.7.0|0.8.0] would require
│ └─ python >=3.10 but there are no viable options
│ ├─ python [3.11.0|3.11.1|...|3.11.6] conflicts with any installable versions previously reported;
│ ├─ python [3.10.0|3.10.1|...|3.10.9] conflicts with any installable versions previously reported;
│ ├─ python 3.12.0 conflicts with any installable versions previously reported;
│ └─ python 3.12.0rc3 would require
│ └─ _python_rc, which does not exist (perhaps a missing channel);
├─ truststore 0.8.0 would require
│ └─ python >=3.10,<3.11.0a0 , which conflicts with any installable versions previously reported;
└─ truststore 0.8.0 would require
└─ python >=3.11,<3.12.0a0 , which conflicts with any installable versions previously reported.
which could have been solved by adding python=3.8 to when mamba was installed.
This feature would mainly be usable for debugging installs.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
[x] 1. Is it tagged with a type: defect or task?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.
[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system? (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest release branch? If yes, is there any issue tagged with release (create if needed)?
[x] 5. If the issue is being closed without a pull request, has an explanation of why it is being closed been provided?
Issue Description
It would be useful to be able to add to the mamba creating command line, because sometimes this is needed to get it to work.
For example, #2197 was caused by the following error
which could have been solved by adding python=3.8 to when mamba was installed.
This feature would mainly be usable for debugging installs.
For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.
For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.