-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(workflows): Add support for simulation integration #1999
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Already confirmed the beta header is not necessary on the workflows' side. Also, the review comments you left were already addressed @doctrino |
…sdk-python into POFSP-744-workflows
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #1999 +/- ##
==========================================
+ Coverage 90.48% 90.49% +0.01%
==========================================
Files 139 141 +2
Lines 22418 22491 +73
==========================================
+ Hits 20284 20354 +70
- Misses 2134 2137 +3
|
|
||
|
||
@dataclass | ||
class SimulationInputOverride(CogniteObject): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the motivation to move this to a separate .py file?
Is it expected to be used with the simulator endpoints?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exactly. there will be many more simint classes added, @lpereiracgn is working on another PR for that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to move this into /data_classes/simulators/<something>.py
? See for example what we did for hosted_extractors/
. The thinking is that with more resources we start to get overlapping names, so we want to separate them into "namespace" which in python would be different packages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will be good to get this one in, but two things.
- Can you update the API docs to match what is actual there? This will cause a lot of confusion if it deviates.
- A few smaller things, see the comments.
Co-authored-by: Anders Albert <[email protected]>
Co-authored-by: Anders Albert <[email protected]>
…sdk-python into POFSP-744-workflows
…sdk-python into POFSP-744-workflows
if TYPE_CHECKING: | ||
from cognite.client import CogniteClient | ||
|
||
_WARNING = FeaturePreviewWarning(api_maturity="General Availability", sdk_maturity="alpha", feature_name="Simulators") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice
…sdk-python into POFSP-744-workflows
Description
Please describe the change you have made.
Checklist:
If a new method has been added it should be referenced in cognite.rst in order to generate docs based on its docstring.