GithubHelp home page GithubHelp logo

Comments (7)

jeffbaumes avatar jeffbaumes commented on June 16, 2024

This one has to do with the names given to analysis activities. Are we able to name the workflow actions differently for metaG and metaT for clarity? The activities in question are "Metagenome assembly XXXXX_XXXXX" (should have a name like "Metatranscriptome assembly XXXXXX_XXXXX" for metaT) and "MetagenomeAnnotation activity for gold:GpXXXXXXX" (should have a name like "MetatranscriptomeAnnotation activity for gold:GpXXXXXXX" for metaT).

from nmdc-schema.

dehays avatar dehays commented on June 16, 2024

I'd like to get @scanon @emileyfadrosh input on this. The issue is that while we differentiate at the omics_processing level (DNA was sequenced or RNA was sequenced), the assembly and annotation are the same analysis workflow. At one point Emiley had suggested calling the analysis simply "Annotation" because both metaT and metaG use the same analysis workflow. I'd like Emiley to indicate how things should appear in the UI and Shane to weigh in on differentiating (if necessary) in the analysis workflow metadata.

from nmdc-schema.

jeffbaumes avatar jeffbaumes commented on June 16, 2024

In an email thread @emileyfadrosh indicated these should be specified/named differently in the analytic workflows. This requires a change in the schema by @wdduncan and a change to the pipeline by @scanon. Then @jbeezley needs to change the ingest.

from nmdc-schema.

ssarrafan avatar ssarrafan commented on June 16, 2024

@scanon and @wdduncan is this something that can be done in the next week or two or should it be moved to a future sprint?

from nmdc-schema.

wdduncan avatar wdduncan commented on June 16, 2024

@scanon do you need a schema change for this?

from nmdc-schema.

wdduncan avatar wdduncan commented on June 16, 2024

@scanon just to confirm, you need the class/type MetatranscriptomeAnnotationActivity. Right?

In the schema file it will be metatranscriptome annotation activity.

from nmdc-schema.

dehays avatar dehays commented on June 16, 2024

We need to differentiate metagenome analysis from metagenome analysis in two places.

Currently there are nmdc:MetagenomeAnnotation and nmdc:MetagenomeAssembly

To the schema we need to add nmdc:MetatranscriptomeAnnotation and nmdc:MetatranscriptomeAssembly and @scanon would need to modify how the type is set in metadata to use these two new analysis types.

Change requested to the two metaT workflow metadata: microbiomedata/metaT#8

from nmdc-schema.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.