Computation in debug mode #117
Merged
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
Signed-off-by: Thang PHAM <[email protected]>
Signed-off-by: Thang PHAM <[email protected]>
Signed-off-by: Thang PHAM <[email protected]>
Signed-off-by: Thang PHAM <[email protected]>
|
dbraquart
approved these changes
Aug 5, 2025
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.
When a launch is performed with the debug option enabled, a debug directory (i.e., debugDir) is always created. Each computation must then pass this debugDir to the Powsybl layer via its computation parameters, for example see code.
At the Powsybl level (see see code), if debugDir is provided, then at the end of the computation, all files from the working directory are systematically copied into the debug directory. Typically, there is always something to copy (for binary computations, at minimum the result is exported. For Java computations, logs are generated due to the presence of debugDir in the parameters.).
In some cases, the working directory may be empty, for example, if an exception was thrown early in the process, but the debug directory is still always zipped and uploaded to S3.