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.
Confusing variable name
See original GitHub issueThe variable ext_ct:
can be mistaken for “extension for CT images”, whereas it refers to MRI (nifti) images. Why the name ‘ct’?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Confusing variable names - Exakat
Adding a figure at the end of a variable name, 0, 1, 2, 3 (sometimes up to 22), or the first letters of...
Read more >Data Scientists, Your Variable Names Are a Mess. Clean Up ...
A variable name should describe the entity the variable represents. When writing your code, ... Unhelpful, confusing or vague variable names.
Read more >Bad Variable Names to Avoid ♀️ | SamanthaMing.com
Bad Variable Names to Avoid ♀️. In an earlier post, I mentioned how you can give your boolean variables a better name by...
Read more >Avoid using x and y as variable names to prevent students ...
Avoid using x and y as variable names to prevent students from confusing variable assignments with mathematical expressions. · More about this tip...
Read more >Naming Variables | Treehouse
Many programmers use variable names that combine two or more words. It's common to name those variables by either connecting the words with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
yes, i did see the comments but it didn’t help me 😅 . I’ll suggest something
Thank you @mariehbourget, I figured out after running the debugger that it was not a typo (I thought that someone wrote “CT” but was thinking “MRI” instead), but that the part common to all modalities (including MRI) comes later:
https://github.com/ivadomed/ivadomed/blob/d1b9e118f491d9e5e88523f8d0f0cae65b26ecca/ivadomed/loader/bids_dataframe.py#L110
I will suggest some comments to clarify the code for someone not familiar with BIDS (I am familiar with BIDS but was nevertheless confused about this chunk of code, why we have sections with microscopy/CT and not with MRI, etc.).