Venue Stampede is now available for Batchsubmit.

Support

Support Options

Submit a Support Ticket

 

Questions and Answers

Status: Accepting answers

0 Like

Anna C Birely

Why are groups split up by file in inDEED when they are not in the specimen authoring tool? Can this be avoided?

In the Specimen Authoring Tool for inDEED, a group can contain sensors from multiple data files and these appear together in the tree structure and only one thumbnail for the group image appears in the top right of the session. However, when opening the inDEED file with inDEED instead of the Authoring Tool, the sensors are sorted first by the .csv file in which the sensor data is listed, then by group, causing the sensors for one group to be split up into different locations. Additionally, a separate thumbnail is made for occurrence of the group within the tree structure.

What is the reason for the difference in the presentation of the sensor information between the Authoring Tool and inDEED? Is there some way to turn off the sorting by .csv file in inDEED?

I recognize that having all sensors in one .csv file is certainly an option, however, it makes the data outside of inDEED less manageable. Having separate files as many researchers likely would prefer and an additional one with all data together for the sake of inDEED has the potential to confuse and doesn’t seem like a reasonable use of space within the project warehouse.

Report abuse

2 Responses

  1. 0 Like 0 Dislike

    George A. Howlett

    Please correct me if I’m wrong. You have different files representing separate parts (sensor readings) of the same experiment.

    The idea behind the extra hierarchy in indeed was that each data file could represent a different trial, repetition, or even experiment. In this case, I definitely want to know from which data set I’m selecting sensors.

    You instead have data files that represent different parts of the same trial or repetition. So the extra hierarchy for the data file isn’t meaningful and more likely to be confusing to the user.

    As you say, you can merge the files into one. This is kind of clunky especially if they are vastly different lengths (such as krypton sensors and non-krypton sensors). I do think we can figure out some mechanism that would allow the data files to be loaded into a virtual dataset, assuming there aren’t duplicate sensors. mydataset::file1.csv mydataset::file2.csv mydataset::file3.csv mydataset::file4.csv

    Instead of using the file name for the data set, the name “mydataset” would be used. The sensors could still be different groups (or not) depending on the authoring file.

    I probably need to work on the syntax (colon is significant for Windows).

    Reply Report abuse

    Please login to answer the question.

  2. 0 Like 0 Dislike

    Enrique Villalobos

    Anna,

    When you create an authoring file (.ind) the only information saved is the sensor header information (name, sensor type, units, etc), and sensor location in the specimen view. Having said that, there is no way the authoring file knows that certain sensors belong to one data file and other sensors belong to a different data file. It does not matter if you loaded your sensors from a data file to create the authoring file, this information will not be saved.

    You are right, if you open two data files, even though they use the same authoring file, then the sensors will be separated by data file in the tree view and the thumbnails will be repeated. Right now that is the way things work, and the only way to avoid this is to have a data file with all the sensors. The reason why this is can be best answered by the software developers rather than me. I know this is a painful process and may not be practical.

    You can always open one data file at a time so that the tree structure and thumbnails will not be duplicated, but you will only be able to plot the sensors within that data file.

    If you want this to change I encourage you to submit a wish, and then it will be taken into consideration.

    Hope this helps.

    Enrique Villalobos NEES Grad Student

    Reply Report abuse

    Please login to answer the question.