Skip to content

Start write up process #30

@slarson

Description

@slarson

Bigger goal is that the next person who comes to this repo; knowing nothing about what we were trying to do, what we got done, would be to able follow some steps and run code that were created, and know enough to understand why they were doing that.

High level

  • Define the scope for what's in the repo, with purpose
  • Organize scripts under folders that break out the different sub parts of the project
  • Write all this stuff below in github markdown, initially in the README.MD
  • Feel free to use screenshots.

Movement stuff

  • Downloading from Zenodo
  • What is Zendodo?
  • What libraries used? What code written?
  • Creating standard yaml files
  • What TF is yaml? And why?
  • updating POW metadata upload (creating & updating classes)
  • Why bother? What does it help?

Standard worm

  • Why do this?
  • Opening images in FIJI
  • Pointing to the original data
  • Using FIJI image tools to perform activities
  • Marking nuclei
  • Straightening
  • Transforms (with new plugin, which one, how to install?)

Dynamical data

  • What is it? (point to it)
  • What's the intention? (i.e. standard yaml files)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions