Forum Replies Created
-
Posts
-
I am migrating a Path database into ST-Sim, and ran into something that’s not in the tutorial. It appears that ST-Sim multipliers operate on transition groups rather than transition types (like in Path). I could create transition groups for every transition type, but since the number of groups a type can be associated with is limited, this solution reduces options for grouping. Or is this limitation no longer in existence? Thanks.
For version 4, did you change the database validation rules in the table field properties or did you change something in the Path software? The ILAP “GIP tool” that generates modeling strata may create a strata that’s less than 5 acres. So will strata such as this be added as a record or do the validation rules prevent this from occuring? (In which case the GIP Tool may not work). If you changed the Path software, however, does this mean that these small strata will be created but not run or return results, or???
Thanks Colin. We had already done the “Compact on Close” as well as “Compact and Repair” options, as well as deleting results, but he said that he was still seeing a substantial increase in DB size after every run. I wanted to check with you to make sure there wasn’t anything else going on before we went to plan B (copying results to a new DB)… I’ll pass along your comments so he can double check if in fact he was seeing an increase in DB size even given your suggestions.
I re-ran the simulation, checking “save output to database” along with my output parameters and I still get this error message. The TransitionsSummary.csv, TransitionsByClassessSummary.csv, and ClassessSummary.csv output tables are blank, although the detailed classes and transitions output tables have data.
However, it works when I uncheck “retain intermediate VDDT files”. BUT, I need to retain these values so I can do post processing on the TransitionsByClassessSummary.csv table….