21 conversion between db and computational data #23
Conversation
This file contains hidden or 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
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.
This branch aimed at simplifying the data format conversion between the data model responses and the format used for the influence diagram and decision tree (and later for the general quantitative part of the tool).
It introduces classes in the service layer with validation tools and conversion to and from json objects. It also introduce an analysis module for the computation part. Classes defines new types with limited associated functionalities (methods). Main actions on these classes are externalized in different modules. This replaces the module src.v0.services.structure_utils which has been suppressed (together with its associated tests).