-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* AMICI-related * Update to AMICI v0.11.2 (#295) * adjoint preequilibration * reduced memory requirements * Make proper use of amici::RDataReporting to avoid computing costly disregarded results (#296) * Add script / cmake target to update amici (Closes #288) * Handle AMICI failures more gracefully * Fix misc/rebuild_amici.sh in case of changed AMICI SWIG interface * Fix: HierarchicalOptimizationWrapper: Return full parameters and full gradient even if nothing computed analytically * Fix C++17 in CMakeLists template * Fix: Use absolute path in misc/setup_amici_model.sh * Fix PEtab import issues * Fix icpc option overriding warning (Closes #220) * Update example notebooks and run on github actions (#294) * Add CLI option to simulator to run simulations with nominal parameters (#293) * Various cleanup * #287, #285, #271, #270, #268, #267, and others * Remove obsolete parpeamici/steadystateSimulator.cpp * Remove outdated amiciHelper.py module for parsing AMICI source files * Remove all uses of std::tmpnam * Handle IpOpt reporting obj_value 0.0 in case of non-finite fval or gradient (#221) * Base image ubuntu:19.10 (EOL ubuntu:19.04) * adapt dataprovider and simulatio to df to third column in simulation condition table (#272) * Update gsllite (#269) * Fix petab import when online some measurements have preequilibrationCondition set * Add basic contribution guide * Fix race conditions in steadystate example (#265) * Cache sonar files on github actions * CI: No shallow clone for running sonarscanner * Remove obsolete and unreliabe functions parpe::launchedWithMpi and parpe::initMpiIfNeeded -- using MPI must be specified via CLI now
- Loading branch information
Showing
1,100 changed files
with
128,601 additions
and
39,854 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,47 @@ | ||
# How to contribute | ||
|
||
We are happy about contributions to parPE in any form, be it new functionality, | ||
documentation, bug reports, or anything else. | ||
|
||
When planning to contribute to parPE, it may be best to first create an issue | ||
at [https://github.com/ICB-DCM/parPE/issues](https://github.com/ICB-DCM/parPE/issues) | ||
to outline plans to avoid any redundant work. | ||
|
||
For any contribution, please create a pull request. By creating a pull request, | ||
you agree on contributing your code/text/image/etc. under the license terms | ||
stated in [https://github.com/ICB-DCM/parPE/blob/master/LICENSE](https://github.com/ICB-DCM/parPE/blob/master/LICENSE). | ||
|
||
|
||
## Style guide | ||
|
||
For any code contributions, please follow the guidelines below. | ||
|
||
|
||
### General | ||
|
||
* All files and functions should come with file-level and function-level | ||
documentation. | ||
|
||
* All new functionality should be covered by unit or integration tests. Runtime | ||
of those tests should be kept as short as possible. | ||
|
||
|
||
### C++ | ||
|
||
* We use C++14 | ||
|
||
* New contributions should follow the | ||
[Google C++ Style Guide](https://google.github.io/styleguide/cppguide.html). | ||
Existing code does not yet, but will be adapted accordingly. | ||
|
||
|
||
### Python | ||
|
||
* We want to be compatible with Python 3.7 | ||
|
||
* For the Python code we want to follow | ||
[PEP8](https://www.python.org/dev/peps/pep-0008/). Although this is not the | ||
case for all existing code, any new contributions should do so. | ||
|
||
* We use Python [type hints](https://docs.python.org/3/library/typing.html) | ||
for all functions. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.