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

Empty output directories

Open
#1 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
matlab, python
Domain
backend

Research direction

Reproduce the Windows run from AnalyzeDeluxe3D.m and follow the traceback through Call_Me_At_The_End.py into Batch_Droplet_Class_Analysis.py, especially the directory listing at line 94. Check how the CoordsAndCurves path is constructed and confirm the fix by rerunning the example until the output directory is populated without FileNotFoundError.

Written by the indexing model from the issue text.

Description

On Windows, there is a scenario where the output/ folder remains empty when running AnalyzeDeluxe3D.m. In the MATLAB output, there is this error message:

Traceback (most recent call last): 
  File "Call_Me_At_The_End.py", line 17, in <module> 
    BDCA.Load_Dict_From_Matfile(test_matfile_file_path) 
  File "C:\Users\Administrator\Desktop\STRESS-main\STRESS-main\Batch_Droplet_Class_Analysis.py", line 54, in Load_Dict_From_Matfile 
    Batch_Droplet_Class_Analysis(Loaded_Dict) 
  File "C:\Users\Administrator\Desktop\STRESS-main\STRESS-main\Batch_Droplet_Class_Analysis.py", line 94, in __init__ 
    for index, file in enumerate(sorted(os.listdir(str(directory).replace("\\","/")))): 
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:/Users/Username/Desktop/STRESS-main/STRESS-main/Short_ExampleTifSequence-InteriorLabel-vsx_2.076um-vsz_3.998um-TimeInterval_3.00min-21timesteps-1_analyzed_2022_6_13_18_25/seg3DResults-Quick Edge Detection - Parallelized/CoordsAndCurves_2022_6_13_18_25' 

This error is related to this: https://stackoverflow.com/questions/19187812/os-listdir-cant-see-my-directory

Dominant language
Python
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 campaslab/STRESS

All issues in campaslab/STRESS

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.