Features for V0.55 #118
Merged
Features for V0.55 #118
Conversation
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
Contributor
marcus-neo
commented
Aug 3, 2021
•
marcus-neo
commented
- Changes to the Cache saving and loading methods
- Instead of saving the entire model class object, the model class is deconstructed on save, and reconstructed on load
- Changes to loaded model location in the code
- Loaded models are now fully integrated into their respective model class
- Docstrings for this change has been updated.
- Added new autosave toggling feature
- Introduced new variable var/cache.var.
- Enabling/Disabling autosave will update the var/cache.var flag.
- Whenever Portal starts, autosave will be set based on the value in var/cache.var.
- Autosave is defaulted to false on first start.
- Enabling autosave will immediately create the portalCache file.
- Disabling autosave will immediately delete the portalCache file.
- Created support for Hosted Deployment into Portal
- Added new tab in model registration interface called "Datature API (Coming Soon)"
- (The tab is currently greyed out)
- Upon clicking the tab users can enter Name, API Link, and Project Secret to register their API as a model.
- Subsequent Steps to load/make predictions will not be different from previous methods.
- Introduced option for certain model types to be saved in cache.
- With the introduction of Datature API, saving the credentials (API link and project secret) could be a security breach.
- This new option allows newly created custom model types to specify if they want their credentials to be saved in cache.
- All registered models that have the save_in_cache flag turned off will not have their credentials saved in cache.
- Image predictions tagged to this model will still be saved in cache nonetheless (The registered model key used for indexing has already been hashed).
- Changed default video frame sampling rate from 20 to 1.
- Moved and renamed use_gpu from cache/use_gpu to var/gpu.var.
- hub_models, var and cache folders will no longer be persistent (removed from github), and will instead be dynamically created upon first startup.
Staging Update
Merge develop version 0.5.0 to staging
Staging to Release for version 0.5.0
Develop to Staging for changes in readme
Staging to Release for the readme changes
Develop to Staging changes in package lock
Staging to release change in release version
Develop to Staging for changing the release name
Staging to Release for changing the release name
Add bash shell in the release workflow
Add bash shell in the release workflow
Final bug fixes
Staging to Release final bug fixes
Develop to Staging for the icprenderer change
Staging to Release for icprenderer change
1. Saving cache no longer saves the entire model class. Instead, only the model type, name, directory and description pertaining to the model class will be saved. 2. Restoring models from cache now takes the model type, name, directory and description and dynamically builds and registers the model.
Update feature_request.md
Update README.md
mask support wip
This is because tensors were not required at that stage
Added backend support for this change
This is to protect secrets from being cached
Feature/cache option
Feture/hosted deployment
1. Greyed out Datature API tab 2. Fixed pylint errors 3. Edited docstring for custom model classes 4. Edited contribution.md
…erval Hotfix/change default frame interval
gkeechin
approved these changes
Aug 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.