Thanks everyone for your feedback today in @ALSDAawg on who we can contact for feedback on our assay metadata!
As always, we rely on you all to ensure that our repository has the most accurate and comprehensive scientific information possible. We are one of the few repositories collecting and curating biological metadata from phenotypic/non-omics assays, so your expertise and networking is critical for our mission.
Powerpoint from today’s ALSDA AWG Meeting - review of current configs that need SME feedback. Includes links to the drafts for each assay.
Public Config List (includes both published and in-progress configs) - This document also has a tab with a FAQ about configs, if you want further information about what we mean by ‘config’.
Please don’t hesitate to message myself or Ryan is you have questions/comments/feedback/complaints.
Rachel
2 Likes
Hi Rachel, @rachelrgilbert
I’m interested in the SME task for Astroskin
regards
Brian
2 Likes
That would be great! Thank you so much. Feel free to leave feedback directly in the sheet, or email the feedback to me. Whatever is easiest for you. My email is rachel.r.gilbert@nasa.gov
1 Like
Thanks so much @brian.russell
Here is the link to the Hexoskin assay metadata/settings config: Astroskin Metadata Config Draft - Google Sheets
Both @rachelrgilbert and I can help guide/answer questions
Hi Ryan,
Looking at this like I am not sure of the intent.
Is this link a validation protocol or an API type explaination of data?
Brian Russell, PhD
Auckland University of Technology
E brian.russell@aut.ac.nz
M +64 22 378 6093,
M +1 650 265 1823
This is our ‘configuration’ metadata standard about the Hexoskin as an assay, so when several Hexoskin datasets are compared, any potential confounds, different settings, or different setup/analysis condiitons are captured. Helps transparency and reproducibility.
If you check out any OSD dataset, go to the ‘assay’ table. These are the column parameters we want to be captured
This example is an example from an Atomic Force Microscopy dataset in OSDR (OSD-702)
Circled below are the parameters we are establishing for Hexoskin/Astroskin (but this example is AFM)
We also will be looking to capture (and get consensus) for standards on any raw, processed, or tabular data files themselves (any dependent variables)
@rachelrgilbert @shawnapandya
1 Like
Like Ryan said, it’s basically the data that we need to collect about how the experiment was performed, which helps ensure reproducibility/repeatability of the experiment.
I added links with the API and the data output examples because it helped inform the first iteration of the draft, and it helped me to understand the data measures that we should anticipate.
But the config itself it focused on the equipment, how it was set up, what information we need to collect about the participants, etc. Basically we want to make sure we are accounting for any parameter that might vary across replicates. For example, the protocol documents describe the types of conductive gel to use for the electrodes, which means that different labs/users might use different types that could affect the results, so I included that as a parameter. Same for other garments, since they are wearing this device on top of clothing. I also tried to account for any pieces of the equipment that were optional, such as the headband. But if you can think of any other technical aspects that we need to consider for wearable devices like this, please let us know!
2 Likes
thanks for the explanation, I’ll add a few things. Protocol information that will help with noise and accuracy outside of device config will likely include movement artefacts and sweat bridging and electrodes drying.
2 Likes
