Dependant columns in log template

Hi,

I have an issue I'm sure many would have come across:

On a multiple plot (log template), I have several columns of data. I apply an output condition on each data record (like the soil unit check on depth). The condition is then checked for each column and it takes ages to produce the output. Would there exist a trick to allow doing the check only once (per table of course)?

If not, that would be great in a future version of gINT (like having dependant columns like for tables...)!

I hope it makes sense!

Thank you

Jerome

  • I am not exactly sure what you are looking for but here are some possibilities that may or may not help.

    1. All entities have an Entire Entity output condition on the configuration tab.  This will cancel printing of the entire entity if false and will not evaluate any other arguments in the entity.

    2. If you are repeatedly evaluating the same condition in multiple entities on a per record basis it might be desirable to set up a field for that condition. The field can be automatically populated using a gINT rule in the table and can even be hidden if you do not want users to see it. This may be what you are getting at when you said "dependent columns". All your log entities then access just the check field that was previously calculated in the table.

    3. I have rarely found that redundant checks or long complex expressions make any appreciable difference in log generation time.  Thus I would look for other items that may be increasing the time (large bitmap images, boring location plans, etc.)

  • Hi Jerome

    You can make User Report Variables for the these Output Condition calculations, and URV are calculated once per PointID (Keyset).

    regards

    Phil

    Phil Wade
    Datgel
    Bentley Channel Partner and Developer Partner
    E: phil.wade@datgel.com | T: +61 2 8202 8600 & +65 6631 9780

    Get the most out of gINT with Datgel Tools.

  • Thank you Szang,

    I have no bitmaps, etc... so it's definitely my SQL queries on the output conditions that take this time, which I can understand, I am asking the software a ridiculous amount of times the same question!

    I'm aware of item 1, it cannot help here.

    I have set up in the past such a field as the one fo your item 2 (at POINT level), that help a lot. But now I filter at depth level so it doesn't work I think

    Jerome

  • Hi Phil,

    thanks for your reply.

    I think I understand what you mean, let me try again... I'll let you know

    Jerome

  • Phil,

    I've had a look at this. Yes we can do very interesting things with them. Unfortunately, I think it doesn't apply to my case because the variable I want is not only Point dependent but also Depth dependent...

    Jerome