search

BlueQuartzSoftware / DREAM3D

Data Analysis program and framework for materials science data analytics, based on the managing framework SIMPL framework.
http://dream3d.bluequartz.net
Other
163 stars 76 forks source link

Advanced Settings Are Not Transferred in Exported Pipelines (V5) #157

Closed tuks188 closed 10 years ago

tuks188 commented 10 years ago

also general issues with not finding advanced fields when a favorite is loaded

imikejackson commented 10 years ago

Which specific filter is this occurring on? This would occur if the filter's writeSettings or readSettings are missing some of the FilterParameters.

tuks188 commented 10 years ago

You're going to hate this answer but it happens everywhere. I cannot be more specific. For instance, I gave Tyler a pipeline with 15 or so filters and all the advanced settings were wrong. Possibly because it's going off of the dream3d file in preflight and since my system path is in there it doesn't know what to do.

Joseph C. Tucker, Ph.D. joetucker@alumni.cmu.edu 412.400.7999

On Jun 17, 2014, at 10:31 PM, "Mike Jackson" notifications@github.com wrote:

Which specific filter is this occurring on? This would occur if the filter's writeSettings or readSettings are missing some of the FilterParameters.

— Reply to this email directly or view it on GitHub.

tuks188 commented 10 years ago

The problem is when I give an exported pipeline to someone else, it has my system path to the DREAM.3D data file so when the new system can't find it, it blows away all the fields for the rest of the pipeline. 2 ways to address this:

1) the new user opens the pipeline file in a text editor and changes the path to where the data file is on their system

2) the original user enters a relative path, e.g. the Data folder within the DREAM.3D distro, and either gives the new user a new build or makes sure they place the data file in the same exact location as you did