Riad KACED wrote:
> Hi There,
>
> A quick glance at your code shows you are using the 'system' skill
> command to process your data.
> Well, 'system' pawns a separate UNIX process to execute a command. But
> once the command thrown outside skill using 'system', no interaction
> is left In other words, you skill script will continue its execustion
> up to the end regadless the progress of the command sent with
> 'system'.
I don't think so. I'm lazy to verify this formally right now, but as far
as I remember system() will
run the command through the shell, and hang until the shell returns. So I
guess, unless you
explicitly launch your command as a background process, it will really
wait until completion.
Even so, I don't know why you are launching a separate ocean process ;
your procedure is evaluated
in ocean already...
> ex****t enob=oceanEval("ENOB(127 256 5)")
This is the part that tickles me... A little up, where your procedure is
defined, the function name
is spelled differently :
> procedure( ENOBS( M N SamplingPoint)
If that's not simply a typo in your post, could well be a source of error
:) But wouldn't explain
why the files are created on the hard disk as you mention (weren't they
here before by any chance ?).
Other than that, the code seems fine. First thing would be to validate it
in Ocean standalone, at
least you'll get proper error messages.
Cheers,
Stéphane
|
