-
Notifications
You must be signed in to change notification settings - Fork 22
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
Small error when calling function cimexport #25
Labels
bug
Something isn't working
Comments
Hi @martinmoraga, I am wondering, why is this issue closed when the associated PR has not been merged yet? Or are the two unrelated? |
Hi @stv0g To be honest I dont know why this PR is closed... Now it is open again ;) |
m-mirz
added a commit
that referenced
this issue
Oct 30, 2024
Depends on cimgen pull request: sogno-platform/cimgen#35, which is already merged now. In my repo all workflows run successfully: tom-hg57#1 (even deploying of github-pages). Improve cimexport.py using profile URIs (from new generated CGMESProfile.py) in model description of exported cim files - Update generated python files created by cimgen - Use profile URIs (from new generated CGMESProfile.py) in model description of exported cim files - Fix "Package information not found" for EquipmentBoundary and ToplogyBoundary in cim_import() by using new generated CGMESProfile.py - Fix export for data read without profile information - Improve cim_export (activeProfileList is now optional - no activeProfileList means output to all profile files with data) - Add function cim_export_to_string_array - Fix model ID in cim_export (must be unique across all files) - Use recommended class profile from new generated classes (if data is read without profile information, or some objects are added after import) - Improve .github/workflows/test.yaml - Update documentation in cimpy/cimexport.py With the new generated python files created by cimgen the issue #23 is solved. PR #24 could be closed if this PR is merged. The same applies to issue #25 and PR #26.
Solved in #39 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sometimes when using the funcion
cimexport
a KeyError Exception occursThe text was updated successfully, but these errors were encountered: