Errors Running Path Spatially

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #1619
    JPriceJPrice
    Participant

    When trying to run Path Spatially, the following errors occur. To address the warnings, I have checked for repeated instances for AltSuccession and Replacement Fire in the models and have found none. The failure is even more of a mystery. Can someone please shed light on the source of these errors and how they can be fixed?

    Thanks!

    Model Builder Starting Model Run for Scenario: [1] – WRLF Base Models without Management
    Model Builder Created Runtime Scenario: [15] – Results for [1] – WRLF Base Models without Management (25-Jan-2012 12.30 PM)
    Simulation Model Running model…
    RunControl ‘Number of Simulation Cells’ calculated from ‘Resolution’ as 10000
    Path Landscape Model Starting Path Landscape Model…
    Landscape Model Starting Model Run
    Landscape Model Exporting Path database to TELSA…

    [Warning] Landscape Model Multiple TST transition groups found for TST transition type ‘AltSuccession’. Using transition group ‘AllFire’ and stratum ‘Boreal_Spruce_Fir_Hardwood_CNTY’.
    [Warning] Landscape Model TSD Groups cannot be specified by stratum in TELSA.
    [Warning] Landscape Model Multiple TST transition groups found for TST transition type ‘ReplacementFire’. Using transition group ‘AllFire’ and stratum ‘Acid_Peatland_Systems_CNTY’.
    [Warning] Landscape Model TSD Groups cannot be specified by stratum in TELSA.
    [Warning] Landscape Model At least one transition with a duplicate stratum, transition type, source state class, and minimum age was ignored.
    Landscape Model Successfully exported Path database to TELSA
    [Warning] Landscape Model Replacing existing initial conditions with TELSA initial conditions.
    [Failure] Model Builder Conversion from type ‘DBNull’ to type ‘Double’ is not valid.
    System.InvalidCastException: Conversion from type ‘DBNull’ to type ‘Double’ is not valid.
    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(Object Value, NumberFormatInfo NumberFormat)
    at Microsoft.VisualBasic.CompilerServices.Conversions.ToDouble(Object Value)
    at gi.a(k9 A_0)
    at gi.g()
    at gi.j()
    at gi.a(Int32 A_0)
    at f1.b(Int32 A_0)
    at f1.a(Int32 A_0)
    at fr.b()
    at fr.a(Int32 A_0)
    Model Builder Finished Model Run[1] – WRLF Base Models without Management
    ——————————————————————————————————————

    #1782
    leonardo-fridleonardo-frid
    Keymaster

    Hi Jessica,

    Please post your database to the ESSA FTP site:
    ftp://ftp.essa.com/incoming/

    and I’ll have a look.

    Cheers,
    Leonardo

    #1783
    leonardo-fridleonardo-frid
    Keymaster

    Hi Jessica,

    The reason for this crash is because for your TELSA template database for this landscape you have loaded the LU Map and run the tessellation but have not yet run the spatial scenario setup. Please refer to this post: http://www.apexrms.com/content/path-and-telsa

    It looks like you have missed step 5. Run the spatial scenario setup using the TELSA spatial tools without specifying a planning zone map or operational unit and then try to run the simulation again. Let me know if that works for you.

    The warnings are unrelated to this crash. They are happening because your time since transition groups property for this scenario specifies time since transition groups for each stratum. In TELSA, time since transition groups are global and can’t be specified by stratum so the warning is telling you that for Alt succession the time since transition group used will be the one specified for stratum ‘Boreal_Spruce_Fir_Hardwood_CNTY’ and for Replacement fire the time since transition group used will be the one specified for stratum ‘Acid_Peatland_Systems_CNTY’. I don’t think this is a problem because in your case the time since transition group is always ‘All Fire’ regardless of the stratum.

    Cheers,
    Leonardo

    #1785
    JPriceJPrice
    Participant

    Hi Leonardo,

    I am unable to create a spatial scenario. According to the TELSA Spatial log, the process encounters an “Unspecified Error” at the step gisSpatialScenario.RecordPZBECOverlaps.

    Thanks for your help!
    Jessica

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.