Timeline export mode #351
Merged
Timeline export mode #351
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
Signed-off-by: lisrte <laurent.issertial@rte-france.com>
|
flo-dup
approved these changes
May 23, 2024
| @@ -122,6 +140,9 @@ public static DynaWaltzParameters load(PlatformConfig platformConfig, FileSystem | |||
|
|
|||
| DumpFileParameters dumpFileParameters = new DumpFileParameters(exportDumpFile, useDumpFile, exportDumpFileFolderPath, dumpFile); | |||
|
|
|||
| // Timeline export mode | |||
| ExportMode timelineExport = config.flatMap(c -> c.getOptionalEnumProperty("timeline.exportMode", ExportMode.class)).orElse(DEFAULT_TIMELINE_EXPORT_MODE); | |||
There was a problem hiding this comment.
we should keep in mind to write somewhere all the properties which can be set for dynawaltz - it has been decided today to use readthedocs for all powsybl repositories.
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
Fixes partially #307