openworm / openworm/OpenWorm

Output fails when running with duration higher than 2000

Open
#332 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
3.1k
Forks
244
PR merge metrics
No merged PRs in 30d

Description

If this issue is intended to be a bug report, please fill out the following:

Expected behavior
Using 0.9.3 image in docker, but whenever I try to run the simulation with command run.cmd -d 2000 or more, it fails.

here is an example:

2023-04-22 02:25:06 >> --------------------------------------------------------------
2023-04-22 02:25:06 >> Command exited with -9: python sibernetic_c302.py
2023-04-22 02:25:06 -duration 2200.0
2023-04-22 02:25:06 -dt 0.005
2023-04-22 02:25:06 -dtNrn 0.05
2023-04-22 02:25:06 -logstep 100
2023-04-22 02:25:06 -device=CPU
2023-04-22 02:25:06 -configuration worm_crawl_half_resolution
2023-04-22 02:25:06 -reference FW
2023-04-22 02:25:06 -c302params C2
2023-04-22 02:25:06 -datareader UpdatedSpreadsheetDataReader2
2023-04-22 02:25:06 -outDir simulations
2023-04-22 02:25:06 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
2023-04-22 02:25:06
2023-04-22 02:25:06 Exiting as the last command failed

Actual behavior

Steps to reproduce the behavior


If this issue is intended to be a beginner issue, please add all of the following:

  • Requirements are clearly specified
  • Links to relevant "getting started" documentation
  • Tagged as "beginner"
  • Tagged with language skill needed to complete
  • Level of difficulty:
    • Trivial = Changing one-line of code somewhere.
    • Standalone = Changes & Development do not affect other components of project. Tasks can be on a critical path, but probably should not be.
    • Simple = from 2 hours work to maybe a week’s work (Thinking + Coding)

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.

Research direction

Start by reproducing the failure with the 0.9.3 Docker image using run.cmd -d 2000 or a duration above 2000, and inspect the Python process exit code of -9. Identify the cause of the termination and verify that simulations above the threshold complete successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, python
Domain
devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.