Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Brainstorm about an improved way to generate numbers

See original GitHub issue

Following minutes of meeting with Alan, I found that we need to find a better way to generate the numbers in FSLeyes.

I am quoting the notes taken from the meeting below,

- have a way to generate them outside of FSLeyes
- increase the size of the numbers, or find another way to generate them. Eg: output image with/without the numbers.

It would be nice if some context can be provided about the issue and we can start discussing this, hence I opened this issue to keep the discussion get started.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:9 (9 by maintainers)

Top GitHub Comments

1reaction

Stoyan-I-Acommented, May 21, 2021

So essentially a _numbers_seg.png file would be generated when the morphometrics are computed, is that correct? For the FSLeyes plugin, we would just load this new file afterwards.

1reaction

mariehbourgetcommented, May 20, 2021

Discussed with @mariehbourget-- great initiative, we should open a PR and replace the number feature from FSLeyes plugin by this new CLI numbering output (ie: FSLeyes will load the numbered axons).

Just a precision: based on the previous comment from Stoyan, @vs74 and I worked on a quick implementation of a _numbers_seg.png file to include with the results when running the morphometrics in CLI for Alan’s project. The plan would be to open a PR about this to include the feature in ADS both when running the CLI and when computing morphometrics from fsleyes.