Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Octave error: Waiting for header #76

Closed
hhgs opened this issue Sep 25, 2013 · 2 comments
Closed

Octave error: Waiting for header #76

hhgs opened this issue Sep 25, 2013 · 2 comments
Labels
Bug Bug not yet in an official release

Comments

@hhgs
Copy link
Member

hhgs commented Sep 25, 2013

For large data set, typically when using dynamic data, the octave communication is not yet stable. Other octave functions with less information copied to octave works ok.

ResInsight 0.9.28 (with octave runned locally) still gives:

10:16:58 Process starting
error: Waiting for header: Network operation timed out
error: evaluating assignment expression near line 4, column 6
error: near line 4 of file /project/res/riOctaveScripts/TimeDiff_SOIL.m' error: feval: the symboljava_exit' is not valid as a function
10:17:29 Process finished

@hhgs
Copy link
Member Author

hhgs commented Sep 25, 2013

The 20 mill cell case with 6 time steps tested earlier with Octave (time-diff of PRESSURE) is now not running. Gives only "waiting for header"

10:35:39 Process starting
error: Waiting for header: Network operation timed out
error: evaluating assignment expression near line 4, column 10
error: near line 4 of file /project/res/riOctaveScripts/TimeDiff_PRESSURE.m' error: feval: the symboljava_exit' is not valid as a function
10:36:12 Process finished

@JacobStoren
Copy link
Member

This is now addressed with an extended timeout (100 min)on data communication. The connection setup itself still has a short timeout of 5 seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Bug not yet in an official release
Projects
None yet
Development

No branches or pull requests

2 participants