- Update to python-bmds v1.0, including BMDS 3.3
- Add full javascript frontend
- Update to BMDS v0.11.0
- Use black to standardize code formatting
- Update libraries to latest versions; including Django 2.1 LTS
- Add CI {tests, black, flake8}
- Update to BMDS v0.10.0
- Refactor application
- Updated deployment procedure
- use ini file instead of environment variables
- add instructions for installing as Windows services
- Update to BMDS v0.9.1
- Update to Bootstrap v4
- Update to BMDS v0.9.0 (added BMDS version 2.7)
- Backwards-compatible updates to dataset API to include new optional dose/response units
- Updated deployment procedure
- Vacuum sqlite3 database after job deletion to propagate data removal
- Update to BMDS v0.8.1
- Use asyncio for drunner tasks (unfortunately, more instable for linux/mac users)
- In addition to catching global errors in BMD execution, try to catch errors the individual dataset level. Therefore, if a batch has a thousand datasets and only one fails, note this, but return the successful results
- Log failed dataset with traceback
- Update docs on deployment procedure and simple R usage
- Update to BMDS v0.7.0
- Updated to BMDS v0.5.4 (don't run models w/ parameters > dose groups)
- Updated to BMDS v0.5.3 (more resilient to bad dataset errors)
- Updated to BMDS v0.5.2 (can run datasets with 3 dose groups w/o failure)
- Updated to BMDS v0.5.0
- Minor updates to output JSON. See details in the output documentation
- For each output, added
dataset_index
integer. - For each model, added
name
,model_index
, andmodel_version
- For each output, added
- For continuous summary datasets, rename
responses
array tomeans
- Added quickstart for using R
- Added the ability to enter continuous individual datasets
- Added new option on requests to allow
immediate
- if True and enabled on the server, a user can request an immediate response to a job, and therefore polling for results is no-longer required. False by default for server performance.
- Initial release