All public logs

Jump to navigation Jump to search

Combined display of all available logs of BCOeditor Wiki. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

Logs
(newest | oldest) View ( | older 50) (20 | 50 | 100 | 250 | 500)
  • 17:03, 4 August 2022 Twang9 talk contribs created page Introduction (Created page with "== Introduction to BioCompute Objects == BioCompute is a paradigm and a BioCompute Object (BCO) is an instance of that paradigm. High-throughput sequencing (HTS), also referred to as next-generation sequencing (NGS) or massively parallel sequencing (MPS), has increased the pace at which we generate, compute and share genomic data in biomedical sciences. As a result, scientists, clinicians and regulators are now faced with a new data paradigm that is less portable, more...")
  • 21:06, 3 August 2022 Twang9 talk contribs created page External-references (Created page with "Back to BCO domains == Appendix-II: External reference database list == This list contains the databases that are currently being used in our BCOs. We use the CURIEs that map to URIs maintained by http://identifiers.org/ Identifiers.org is an established resolving system that enables the referencing of data for the scientific community, with a current focus on the Life Sciences domain. Identifiers.org provides direct access to the identified data us...")
  • 20:12, 3 August 2022 Twang9 talk contribs created page Error-domain (Created page with "Back to BCO domains == Error Domain, acceptable range of variability “error_domain” == The error domain can be used to determine what range of input returns and outputs are within the tolerance level defined in this subdomain and therefore can be used to optimize the algorithm. It consists of two subdomains: empirical and algorithmic. The empirical error subdomain contains empirically determined values such as limits of detectability, false positiv...")
  • 20:07, 3 August 2022 Twang9 talk contribs created page Parametric-domain (Created page with "Back to BCO domains == Parametric Domain “parametric_domain” == This optional domain represents the list of parameters customizing the computational flow which can affect the output of the calculations. These fields can be custom to each kind of analysis and are tied to a particular pipeline implementation. It is recommended that these fields be generated automatically, but that may not always be possible. Please refer to the documentation of indivi...")
  • 19:59, 3 August 2022 Twang9 talk contribs created page Execution-domain (Created page with "Back to BCO domains == Execution Domain “execution_domain” == This section defines the execution_domain part of the BCO. The fields required for the execution of the BCO have been encapsulated together in order to clearly separate information needed for deployment, software configuration, and running applications in a dependent environment. One byproduct of an accurate BCO definition is the facilitation of reproducibility as defined...")
  • 19:45, 3 August 2022 Twang9 talk contribs created page Extension-domain (Created page with "Back to BCO domains == Extension Domain “extension_domain” == The Extension Domain allows a user to define additional fields and is optional. The Extension Domain is for the inclusion of any additional structured information. A valid JSON schema for each extension used in this domain is expected to be specified. The schema should be namespaced, and it is recommended that resolving the namespaced URI will provide the extension’s JSON Schema. The UR...")
  • 18:14, 3 August 2022 Twang9 talk contribs created page Best practices (Created page with "== General == *The required domains are defined by the IEEE. However, a BioCompute Object is considered complete when an Error Domain exists. *Versioning is allowed, but only if the changes do not affect the workflow or output. BCO versioning follows a minor.patch schema, no major versions are allowed (substantial changes result in a new BCO). Minor changes are things like a change of contact information for a contributor, patch changes are things like spelling and gram...")
  • 16:58, 3 August 2022 Twang9 talk contribs created page Top-level (Created page with "Back to BCO domains ==Top Level Fields== These header fields uniquely define this BCO. These fields are required for every BCO and are represented at the top level object. Condensed example: { "object_id": "https://example.com/BCO_948701/1.0", "spec_version" : "https://w3id.org/ieee/ieee-2791-schema/2791object.json", "etag": "d41d8cd98f00b204e9800998ecf8427e", "provenance_domain": {...") Tag: Visual edit: Switched
  • 16:56, 3 August 2022 Twang9 talk contribs created page Provenance-domain (Created page with "Back to BCO domains == Provenance Domain “provenance_domain” == This section defines the fields of the provenance_domain part of the BCO structure. Condensed example: "provenance_domain": { "name": "HCV1a ledipasvir resistance SNP detection", "version": "2.9", "review": [ ], "obsolete_after" : "2118-09-26T14:43:43-0400", "embargo" : { },...")
  • 15:30, 3 August 2022 Twang9 talk contribs created page Bco faq (Created page with "== General == 1. '''Where would information regarding data sources and standard operating procedures be? Which specific domain?''' Data sources should be recorded as described by the input_subdomain in the “io_domain” and the input_list in the “description_domain”. Standard operating procedures and any other information about data transformations SHOULD be elaborated upon in the “usability_domain”....")
  • 15:23, 3 August 2022 Twang9 talk contribs created page Usability-domain (Created page with "Back to BCO domains == Usability Domain “usability_domain” == This section defines the usability_domain part of the BCO structure. The Usability Domain of an Object is a plain language description of what was done in the workflow. This should align with the actual steps described elsewhere in the Object. The Usability Domain conveys the purpose of the Object. It is an array of free text values that should be consistent with the term...")
  • 15:11, 3 August 2022 Twang9 talk contribs created page Description-domain (Created page with "Back to BCO domains == Description Domain “description_domain” == This section defines the fields of the description_domain part of the BCO structure. Structured field for description of external references, the pipeline steps, and the relationship of I/O objects. Information in this domain is not used for computation. This domain is meant to capture information that is currently being provided in FDA submission in a standardized fo...")
  • 13:37, 3 August 2022 Twang9 talk contribs created page Iodomain (Created page with "== Input and Output Domain "io_domain" == This section defines the io_domain part of the BCO. This represents the list of global input and output files created by the computational workflow, excluding the intermediate files. These fields are pointers to objects that can reside in the system performing the computation or any other accessible system. Just like the fields of the parametric domain, these fields are expected to vary depending on the specific...")
  • 20:26, 2 August 2022 Twang9 talk contribs moved page Bhco-domains to Bco-domains
  • 20:26, 2 August 2022 Twang9 talk contribs created page Bhco-domains (Created page with "== BCO domains == A BCO JSON object is split into different parts, or domains, detailed below. Condensed example: "spec_version" : "https://w3id.org/biocompute/1.3.0/", "object_id": "https://example.com/bco/9487ae7e-c1aa-4a3c-b18f-3d3695b33ace", "type": "antiviral_resistance_detection", "etag": "584C7FE128717E1712426AB19CAAEA8BC1E27365B54285BBEA1221284C7D3A48", "provenance_domain": { }, "usability_domain": [ ], "extension_domain":{...")
  • 14:38, 1 August 2022 User account Twang9 talk contribs was created
(newest | oldest) View ( | older 50) (20 | 50 | 100 | 250 | 500)
Retrieved from "https://wiki.biocomputeobject.org/Special:Log/Twang9"