Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fix formatting logging message

Open
  • Is something wrong?
#41 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
45/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Inspect pipeline/gene_to_nissl.py at lines 115-119, starting with the logging statement that produces the reported output. Add the missing spaces in the message and verify that standard output separates the section number, volume shape, and removal text correctly.

Written by the indexing model from the issue text.

Description

https://github.com/BlueBrain/Deep-Atlas/blob/1add6775b6a6d1315dbcace02768aa2974874f11/pipeline/gene_to_nissl.py#L115-L119

We should add extra spaces. I got this in the standard output

WARNING - gene-to-nissl - One of the gene slice has a section number (531.0)out of nissl volume shape (528, 320, 456). This slice isremoved from the pipeline.
Dominant language
Python
Stars
4
Forks
2
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlueBrain/Deep-Atlas

All issues in BlueBrain/Deep-Atlas

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.