CMB issueshttps://gitlab.kitware.com/cmb/cmb/-/issues2022-08-10T19:11:09-04:00https://gitlab.kitware.com/cmb/cmb/-/issues/197Save/restore state2022-08-10T19:11:09-04:00David ThompsonSave/restore stateSaving and restoring state should work in modelbuilder. Currently, there is a problem causing crashes when state files are reloaded.Saving and restoring state should work in modelbuilder. Currently, there is a problem causing crashes when state files are reloaded.CMB 6.0https://gitlab.kitware.com/cmb/cmb/-/issues/196Dashboard2018-10-10T16:04:32-04:00David ThompsonDashboard+ [ ] CMBTests → New CMB tests
+ [ ] Packaging+ [ ] CMBTests → New CMB tests
+ [ ] PackagingCMB 6.0https://gitlab.kitware.com/cmb/cmb/-/issues/195Performance2018-10-10T15:59:28-04:00David ThompsonPerformanceEnsure that large data does not cause problems before the release.Ensure that large data does not cause problems before the release.CMB 6.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/194modelbuilder-forward.c pv_version is not being set correctly2018-12-19T14:39:43-05:00chart3388modelbuilder-forward.c pv_version is not being set correctlyHi,
modelbuilder/modelbuilder-forward.c line 18 is not being setup correctly.
```
#define vtksys_SHARED_FORWARD_PATH_INSTALL "../lib","../lib","../lib/paraview-."
```
This appears to be caused from CMakeLists.txt performing on line...Hi,
modelbuilder/modelbuilder-forward.c line 18 is not being setup correctly.
```
#define vtksys_SHARED_FORWARD_PATH_INSTALL "../lib","../lib","../lib/paraview-."
```
This appears to be caused from CMakeLists.txt performing on line 16 the include(CMBInstallRules) which utilizes PARAVIEW_MAJOR_VERSION AND PARAVIEW_MINOR_VERSION before doing the find_package(ParaView) on line 24 which sets those. If I move find_package(ParaView) before the include(CMBInstallRules) it gets set correctly.
```
find_package(ParaView)
include(CMBInstallRules) # Fetch CMB version from version.txt and set up install/output directories.
```chart3388chart3388https://gitlab.kitware.com/cmb/cmb/-/issues/193Browse Files window different depending on operation2018-09-12T10:59:26-04:00chart3388Browse Files window different depending on operationHi,
In CMB 6 if I go to File -> Open I get a different file explorer than if I go to Operations -> smtk::session::vtk::Read. One has the recent directories I've utilized and the other doesn't.Hi,
In CMB 6 if I go to File -> Open I get a different file explorer than if I go to Operations -> smtk::session::vtk::Read. One has the recent directories I've utilized and the other doesn't.https://gitlab.kitware.com/cmb/cmb/-/issues/192Split SMTK back out of CMB2020-05-07T10:45:00-04:00Ben BoeckelSplit SMTK back out of CMBDiscussion indicates that CMB is not as dependent on SMTK updates as it once was. Once SMTK has a proper SDK installation, the submodule should be removed once again.
Cc: @tjcorona @bob.obara @dcthompDiscussion indicates that CMB is not as dependent on SMTK updates as it once was. Once SMTK has a proper SDK installation, the submodule should be removed once again.
Cc: @tjcorona @bob.obara @dcthomphttps://gitlab.kitware.com/cmb/cmb/-/issues/191Move required ParaView features into CMB2018-09-04T17:27:44-04:00Ben BoeckelMove required ParaView features into CMBThis will allow for a single application to be distributed for all supported use cases. Requires finding out what features need to be exposed in Model Builder.
Cc: @bob.obara @dcthomp @tjcoronaThis will allow for a single application to be distributed for all supported use cases. Requires finding out what features need to be exposed in Model Builder.
Cc: @bob.obara @dcthomp @tjcoronahttps://gitlab.kitware.com/cmb/cmb/-/issues/190Change Post processing Icon2018-10-11T18:46:17-04:00Robert M. O'BaraChange Post processing IconUse a ParaView like iconUse a ParaView like iconCMB 6.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/189CMB6 - Operations Empty upon launching2020-05-06T09:08:56-04:00chart3388CMB6 - Operations Empty upon launchingLaunching CMB 6 the Operations panel is always empty and the "Limit by selection" box is always checked. If I go and unchecked the Limit by selection box under the Operations panel and recheck it the Operations panel is now populated wi...Launching CMB 6 the Operations panel is always empty and the "Limit by selection" box is always checked. If I go and unchecked the Limit by selection box under the Operations panel and recheck it the Operations panel is now populated with the appropriate operations.
Thanks,
CoreyCMB 6.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/188Ability to save and load in CMB/ParaView State2018-10-19T14:52:38-04:00Robert M. O'BaraAbility to save and load in CMB/ParaView StateThis will allow the user to reload in all of the current resources and post-processing data.This will allow the user to reload in all of the current resources and post-processing data.CMB 6.0T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/cmb/-/issues/187UX Review for ModelBuilder2018-08-10T14:56:21-04:00Robert M. O'BaraUX Review for ModelBuilderCMB 6.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/186CONTRIBUTING links are broken on master2018-08-09T16:29:07-04:00Ben BoeckelCONTRIBUTING links are broken on masterWith the new rewrite, docs never made the migration which left lots of broken links in `CONTRIBUTING.md`.
Cc: @dcthomp @tjcorona @bob.obaraWith the new rewrite, docs never made the migration which left lots of broken links in `CONTRIBUTING.md`.
Cc: @dcthomp @tjcorona @bob.obaraRobert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/185Runtime python plugins2017-12-22T09:28:03-05:00Kim PeveyRuntime python pluginsThe python plugin mechanism is great. After doing some development of plugins, I have some ideas that could make things easier for users/developers.
1. Load failure - Error message for failed imports (this is important because when plu...The python plugin mechanism is great. After doing some development of plugins, I have some ideas that could make things easier for users/developers.
1. Load failure - Error message for failed imports (this is important because when plugins use external packages, the PYTHONPATH and env must be set up properly. this will provide a catch for incorrect setup)
2. Load failure - Error message for failed xml description/ui generation
3. Reloading a currently loaded plugin - Warn, then overwrite existing plugin
4. Add 'recent plugins' list or consider persistence on MB close and reopen.5.0T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/cmb/-/issues/184Skewed DEMs load with bad data2017-12-01T12:07:24-05:00Kim PeveySkewed DEMs load with bad dataIf you load a DEM with a slight, or not so slight, skew to it, MB will load the DEM into a straight square and fill in the empty tiles with -32767. ALL DEMs that are not perfectly in alignment with the X-Y plane will have this issue. Thi...If you load a DEM with a slight, or not so slight, skew to it, MB will load the DEM into a straight square and fill in the empty tiles with -32767. ALL DEMs that are not perfectly in alignment with the X-Y plane will have this issue. This becomes a visualization issue when the DEM is loaded (since the automatic range is way off) and these false values are also picked up by the interpolator.
![demskew](/uploads/78ccc70a3f4919411d8299a0faa3032f/demskew.PNG)
This happens on 4.2 and 5.05.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/183DEM visualization after Save-As2017-12-01T11:18:09-05:00Kim PeveyDEM visualization after Save-AsIf I have a DEM loaded into my model and I perform a Save As operation, my DEM will be visualized and the eyeball toggle will have no effect when clicked (eyeball opens and closes, DEM stays visible at all times).
When the saved sm...If I have a DEM loaded into my model and I perform a Save As operation, my DEM will be visualized and the eyeball toggle will have no effect when clicked (eyeball opens and closes, DEM stays visible at all times).
When the saved smtk is reopened, the visibility is fixed.
I have a feeling this may not be consistently reproducible - if you have trouble recreating, try saving into a different directory.4.2.1Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/182Custom scale in display2017-12-01T10:52:13-05:00Kim PeveyCustom scale in displayWhen you toggle between Solid Color and Point Coordinates, it resets to the original scale and looses the previously set custom scale.
Also, the only way to access the 'set custom scale' is to Edit the color map and go to the 'set ...When you toggle between Solid Color and Point Coordinates, it resets to the original scale and looses the previously set custom scale.
Also, the only way to access the 'set custom scale' is to Edit the color map and go to the 'set custom scale' button from there. It would be better if it was available on the Display panel.
Also, its unclear what the 'use separate color map' button does. Sometimes it switches to a different colormap, sometimes it toggles between two different color maps (both different from my custom map).5.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/181Manipulating visualized data2017-11-20T14:48:10-05:00Kim PeveyManipulating visualized dataI have a 150 MB DEM that I've loaded into MB as an auxiliary geometry. Whenever the selection is handled (toggle on or off), the display parameters are changed, or viz is toggled on from previously off, it takes an unexpected amount of t...I have a 150 MB DEM that I've loaded into MB as an auxiliary geometry. Whenever the selection is handled (toggle on or off), the display parameters are changed, or viz is toggled on from previously off, it takes an unexpected amount of time for MB to "think" through the process. With a file of this size, I would expect something as simple as a selection change should occur within, say, a 1 second time frame, not the 15 seconds that I'm seeing.
This isn't a bug, just more of a philosophical discussion on how the viz is handled with larger files (though this is a relatively small file)5.0Robert M. O'BaraRobert M. O'Barahttps://gitlab.kitware.com/cmb/cmb/-/issues/180Mesh- Apply Bathymetry no mesh selection2018-08-09T14:34:37-04:00Kim PeveyMesh- Apply Bathymetry no mesh selectionThere is no way to specify which mesh in which to apply the bathymetry. If there are multiple meshes, which one does it apply to?There is no way to specify which mesh in which to apply the bathymetry. If there are multiple meshes, which one does it apply to?4.2.1T.J. CoronaT.J. Coronahttps://gitlab.kitware.com/cmb/cmb/-/issues/179Model-Export and Model-Save: Crash2018-08-09T14:55:26-04:00Kim PeveyModel-Export and Model-Save: CrashWhen the Model Export or Model Save operator is used, "Show by Category" is checked, and then "Advanced" is selected, MB will crash.
Recipe:
1) Create a new polygon model
2) Go to Model - Export (this recipe will work whether o...When the Model Export or Model Save operator is used, "Show by Category" is checked, and then "Advanced" is selected, MB will crash.
Recipe:
1) Create a new polygon model
2) Go to Model - Export (this recipe will work whether or not model entities exist)
3) Check "Show by Category"
4) Switch from General to Advanced
5) Crash
Side note: The Advanced and Category options should NOT be visible for these operators anyway. See issue #1784.2.1https://gitlab.kitware.com/cmb/cmb/-/issues/178Operators need the advanced and category options hidden2018-08-09T14:30:07-04:00Kim PeveyOperators need the advanced and category options hiddenThere are some operators that need the advanced and category to be hidden from users since there are no additional options that exist for the operator.
The list of operators:
Model - Export
Model - Save
Model entities - Assign...There are some operators that need the advanced and category to be hidden from users since there are no additional options that exist for the operator.
The list of operators:
Model - Export
Model - Save
Model entities - Assign Colors4.2.1