Comments (4)
Hi,
The reason was to limit data/information duplication to a minimum:
Keeping metadata in a file like the panel.csv
as compared to copy this information around makes it clearer that this is the single source of truth for channel metadata and makes it way easier eg to rename channel names (which is extremely common as there is no single standard how to annotate antibody channel names).
Also I do not see how this makes it technically would make It significantly easier to link target names to images for ilastik training or ImageJ, but maybe I am missing something,
Anyways, if you are convinced this is a good idea, feel free to add it.
from imctools.
Hey, agreed on data duplication. Especially since these files are generated for each exported .tiff
(you could think about exporting them per .mcd since you want to enforce a consistent naming scheme anyway). I just find it a bit inconvenient to lookup the target name in the panel based on the metal order in the exported .csv
since the entries are not ordered the same way unless you manually reorder the panel by metal tag. But yes, if it annoys me in the future, I'll add it ;)
from imctools.
Still an open issue?
from imctools.
Well, closing for now
from imctools.
Related Issues (20)
- extract panorama HOT 4
- Make exceptions discoverable in API HOT 3
- Extra 161 bytes extracted on all image buffers HOT 1
- TxtParser and McdParser should share a common base class
- Wrong ROI coordinates for new Fluidigm software versions HOT 4
- Create imctools.data.Acquisition object without loading image data when using TxtParser
- KeyError: 'Name' HOT 11
- ValueError: invalid literal for int() with base 10: HOT 1
- Broken assertion HOT 3
- ome2histocat stripps .tiff file ending from masks HOT 2
- Value Error: No session JSON files available HOT 3
- Error while running IMCtools HOT 4
- Generated OME-XML in OME-TIFF files is not schema compliant due to out-of-order AcquisitionDate element HOT 3
- broken link to xml namespace HOT 1
- imctools.scripts HOT 2
- Typo in method omexml.py HOT 2
- Inquiry about omexml.py related to schema location HOT 2
- NotADirectoryError: [Errno 20] Not a directory: '../../data/ometiff/.DS_Store/.DS_Store_Acquisition_meta.csv' HOT 4
- Adding clear specification of the 'ome' folder HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from imctools.