-
Notifications
You must be signed in to change notification settings - Fork 11
BUG/ENH: Fix Backwards Pipeline Compatibility and Add Testing #1476
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
base: develop
Are you sure you want to change the base?
BUG/ENH: Fix Backwards Pipeline Compatibility and Add Testing #1476
Conversation
|
@nyoungbq Just tried a quick test and I copied the (08) SmallIN100 Full Reconstruction from DREAM.3D version 6.5.171 into DREAM3D-NX and looks like it is mostly correct but I got an error on filter 13 about a missing data array path and the issue was in filter 11 "Compute Feature Average Orientations", the "Feature Attribute Matrix" was not set correctly or transferred correctly from the old pipeline. |
|
@imikejackson okay I will pull all the default pipelines from 6.5.171 and test/patch for them. The mega-pipeline generated for this was from 6.6 |
aa07206 to
cad0018
Compare
cad0018 to
49ac2e7
Compare
73569ef to
0428742
Compare
a9a69f3 to
a566f7e
Compare
- Assorted Parameter Fixes - Conversion Function Updates - Assorted SnxCore filter fixes
a566f7e to
cffd9d3
Compare
Conversion updates
Test Added
Has a sibling branch on
SimplnxReviewThe tool to generate the test data is on the SIMPL repo
Testing Methodology:
6.6a "mega-pipeline" was generated with values according to parameter type. This not only verifies that the values are read in, but that they are read in correctly. Any exclusions (ie new filter parameters) must be explicitly excluded. Any new filter registered to the Plugin UUID conversion maps will be tested automatically.6.5.171every default pipeline was updated to the6.5.171release standard (except synthetics, noted inREADMEin test data). These are validated that the values are read in and that they match the expected type. Any new filter registered to the Plugin UUID conversion maps will be tested automatically, SO LONG AS IT APPEARS IN THE DEFAULT6.5.171PIPELINES.Note any filter that is not in a plugin-level conversion UUID map will NOT be tested.
Also note that just because it reads them in properly does not mean the pipeline cannot be run without errors. Example: consider a real case where an AttributeMatrix was hard-coded to the name
vertex datain SIMPL, thus filters that follow in the pipeline may have the path../vertex data/... However, insimplnxthe filter was made more general and thus usescell dataas the hard-coded AM name, thus filters that follow in the pipeline may have the path../cell data/... When conversion occurs the../vertex data/..is read in properly, but the array actually exists at../cell data/..causing a disparity.