Giter Club home page Giter Club logo

tutorials's Introduction

Collection of eNanoMapper Tutorials

Each folder contains the source of a separate tutorial. This can be a Word document or something else.

Tutorials in HTML

Tutorials in Word

Feedback

For each tutorial, issues and feature requests can be filed in the issue tracker of this repository.

How to cite

Further information can be found in the following reference which can be used as citation:

Lucian Farcal, Philip Doganis, Egon Willighagen, Rob Reedijk, Spela Predan Hardy, Barry Hardy.
(2016). Deliverable Report D6.3 eNanoMapper Tutorials. Zenodo.

DOI

tutorials's People

Contributors

dependabot[bot] avatar egonw avatar fehrhart avatar marvinm2 avatar njall avatar uanaf avatar vedina avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

tutorials's Issues

Adding ontology terms, some things I do not understand

"most ontologies include bits from other ontologies;" is given as a reason to not include full ontologies. This brings up the question why that is a problem. I suppose you mean to say that in that case you will take it from the source ontology if it is relevant in the first place. But ... would it not be relevant to also capture that it, in fact, occurs in both? Or is that something you would figure out elsewhere?

Under "Adding a terms from an already used ontology" (there is "a terms" must be a typo btw) it says:
"where in the eNanoMapper ontology should your selection show up?". That suggests it could show up under something that is not from that same (already used) ontology. Does that really make sense? Can you have 1) a branch that is below an existing branch from the same ontology but no longer connected via terms from that ontology (that feels strange, maybe, in that case, you should improve the source?) 2) have two branches used from an ontology but not use the part directly on top of both? That too feels strange, but I could imagine using wider terms at some stage, allowing the addition of parallel branches from other ontologies. I think that at least would need some review.

Please check CLW info

Freddie, I am copy/pasting CLW info from the document, but not sure if this is always correct. Can you please check it, and correct if needed (in both the readme.md and the Word file)?

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.