You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you save an output file from rivet_console, then load it in the RIVET GUI, it presents the computation as if it is a 0-dimensional homology computation, regardless of the dimension computed in rivet_console. i.e. the line at the bottom that describes the dimension always says "0".
I imagine either the dimension is not stored in rivet_console's output, or perhaps the GUI does not read it properly. This is more of an expositional problem, rather than a bug, but it can lead to confusion.
The text was updated successfully, but these errors were encountered:
To add to this, in our pull request, some RIVET files (namely those constructed from
'firep' input) may not have a homology dimension at all, and homology dimension should be "N/A."
In fact, for firep input files the bottom of the main window also shows homology dimension 0 when it should show N/A, though the file input dialogue does already show N/A.
mlesnick
changed the title
rivet_console output does not store dimension
rivet_console output does not store homology dimension
Dec 11, 2019
mlesnick
changed the title
rivet_console output does not store homology dimension
module invariants file does not store homology dimension
Dec 11, 2019
If you save an output file from rivet_console, then load it in the RIVET GUI, it presents the computation as if it is a 0-dimensional homology computation, regardless of the dimension computed in rivet_console. i.e. the line at the bottom that describes the dimension always says "0".
I imagine either the dimension is not stored in rivet_console's output, or perhaps the GUI does not read it properly. This is more of an expositional problem, rather than a bug, but it can lead to confusion.
The text was updated successfully, but these errors were encountered: