Menu

#1737 Hang after save

Marx
closed
None
1fatal
2024-02-09
2024-02-07
Steve Keen
No

I was really pleased to do what this model did, only to have it crash on me--even after I fixed what I thought was my mistake that may have caused the crash.

The screenshot shows the pre-saved functional file. I was trying to illustrate the difference between perfect competition and monopoly in Neoclassical economics using Ravel--I had tried in Excel and it was a nightmare with cell reference formulas, and I was initially delighted at how easy it was to do in Ravel--before this crash.

The one thing I couldn't do in Ravel--which I had to first do in Excel--was create an array of numbers to represent quantity produced. Initially I did that with a single column of numbers, which I imported as an axis, and then I did all the formulas on that.

When the crash occurred, I finally surmised that this could be the problem--just importing an axis--so I created a second file where I had an Index in one column (which became the dimension) and then the same numbers as "q" in the second. That worked really well, so I thought I'd cracked it--and then it crashed on load!

I'll send a movie of the crash after this--it's too big for SourceForge.

17 Attachments

Discussion

  • High Performance Coder

    Apart from a pedantic quibble on the use of "crash" for "hang", I agree this model hangs on loading, at least on 3.2.-rc.1. And that should not be, so needs to be fixed.

    A hang is where the program becomes unresponsive to input, but continues running. A crash is where the program terminates unexpectedly. Sometimes known informally as a "core dump" or "segfault".

     
  • High Performance Coder

    Ticket moved from /p/minsky/ravel/457/

    Can't be converted:

    • _priority: 1Fatal
     
  • High Performance Coder

    • priority: 1Fatal --> 1fatal
    • Milestone: Pascal --> Marx
     
  • High Performance Coder

    PCvsMonopolyFixAttempt01.mky does seem to reproduce this issue, at least with 3.2.0-rc.1

     
  • High Performance Coder

    It was a bug. For some reason some of the plots had data attached on the RHS, but not the LHS. This caused it to enter an infinite loop multiplying by zero, and expecting something to change. Although I can't see that in the model when finally opened.

     
  • High Performance Coder

    • status: open --> closed
    • assigned_to: High Performance Coder
     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB