Opened 17 years ago
Closed 17 years ago
#534 closed defect (worksforme)
Warning in the evaluation window
Reported by: | fjmolina | Owned by: | Víctor de Buen Remiro |
---|---|---|---|
Priority: | highest | Milestone: | |
Component: | System | Version: | 1.1.6 |
Severity: | blocker | Keywords: | |
Cc: | lmartiles |
Description
I obtained the following warning message when running a script
Warning: [2721] OIS:
Cannot rebuild virtual expression of non bounded TimeSet Mensual=(tmsAn)
Only cached dates will be accessible between [y1993m01d01,y2007m12d31]
To avoid this problem save just bounded time sets
This problem does not appear in the window's version: only in the linux's version.
Victor: if you have any doubt, please make contact with Artiles.
Best regards,
Javier
Attachments (1)
Change History (6)
comment:1 Changed 17 years ago by
comment:2 Changed 17 years ago by
It seems that the warning messages are produced by
Set Ois.Load(PathDatos +"Amp.Cob.EV2.C7.oza")[1];
in
blk_data.tol
that is called from
loadModel.tol
comment:3 Changed 17 years ago by
Sorry, I've no idea what are you talking about. I know nothing about loadModel.tol, blk_data.tol, etc.
I will need a set of to expressions or files to reproduce the problem in my computer in order to detect and solve this problem, if it is not solved yet.
comment:4 Changed 17 years ago by
Javier, could you attach to this bug the file Amp.Cob.EV2.C7.oza? You can use this link http://bugs.tol-project.org/attachment.cgi?bugid=534&action=enter to do it.
regards,
Jorge
Changed 17 years ago by
Attachment: | Amp.Cob.EV2.C7.oza added |
---|
This is the file that is not properly loaded.
comment:5 Changed 17 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
Well, this OIS image was created by host ZEUTHEN with Windows at 2007-11-27 17:45:59.00 with an unstable version of TOL
v1.1.6 b.0.25.alpha 2007-10-09 17:37:01 i686-win
The OIS image was created when there was a bug in TOL, the bug was solved, but the created file was not rebuilt again. So newer TOL can't fix it, it only can read it as is: wrong.
So, all you need to do is to rebuild it with a newer stable version, because this bug has been solved already. If you don't have the TOL code needed to rebuilt it, then you can do nothing about this problem.
Have you to try using last build of version 1.1.6 ?
If not, try it because it has been already probably solved, else send me a TOL-code to reproduce this problem.
Thanks