14-10-2024, 04:41 PM
Good morning,
I have been doing some testing to migrate to Veda 3.1.3.0 (from 3.1.1.0). I have observed a new Message in the Sync Log summary : "The process is not defined for this region". I got this message for processes, in a VT file, that are not supposed to be read as they have a * in the region column. I am wondering if something changed here for how things are read or not with the *, as we were using the * in the region column (first column of the FI_T table) for process not to be defined (mainly when the PRC_RESID are to be 0) but that we want to keep in our table in case for some other calibration it now get a PRC_RESID. With this message it seems that the line is now read and I now get a warning for this lines.
Thanks for any clarification on this,
Marie
I have been doing some testing to migrate to Veda 3.1.3.0 (from 3.1.1.0). I have observed a new Message in the Sync Log summary : "The process is not defined for this region". I got this message for processes, in a VT file, that are not supposed to be read as they have a * in the region column. I am wondering if something changed here for how things are read or not with the *, as we were using the * in the region column (first column of the FI_T table) for process not to be defined (mainly when the PRC_RESID are to be 0) but that we want to keep in our table in case for some other calibration it now get a PRC_RESID. With this message it seems that the line is now read and I now get a warning for this lines.
Thanks for any clarification on this,
Marie