Forum Replies Created
-
AuthorPosts
-
leonardo-fridKeymaster
Hi Brian,
There are two issues for the files that you sent. The data type for spatial initial conditions rasters is integer and yours was 64 bit float. In principle this would be ok if you still only had integer values for each cell. However, the no-data value specified for these rasters is -1.797693e+308. Maybe you could change the NO_DATA value to -9999 and try again?
Let me know if that works.
Cheers
Leonardo
leonardo-fridKeymasterHi Brian,
If you send me the files you are trying to import, I will try to find out what the error is.
Thanks,
Leonardo
leonardo-fridKeymasterIn order to simplify the interface for new users we have added a hidden field feature to a number of the scenario properties and definitions. Fields that are optional are now hidden by default. In order to view them, all you need to do is right click on the property table (in ST-Sim) or unhide the fields (in Excel).
leonardo-fridKeymasterI just tried this on my workstation with version 1.4.2 and was not able to reproduce the error with your files. Can you confirm that there are no rasters being used for ages, secondary strata or multipliers? If there are please check that these are also identical.
leonardo-fridKeymasterAccording to the error message, the X coordinate for the lower left corner of the rasters is not identical. If you look at the values for the rasters and they are identical then send them my way and I will try to find out what really is the problem.
Regards,
Leonardo
September 27, 2013 at 5:14 pm in reply to: Output CSVs from model runs (column definitions for PATH) #1832leonardo-fridKeymasterNote that Path 3.1 tracked state class and transition group codes whereas Path 4.2 does not. It just tracks the names. Note also that Path 4.2 can have multiple scenarios in one output file whereas Path 3.1 cannot. Here are the crosswalks for the appropriate fields. Let me know if you have other questions.
State Class Summary:
3.1, 4.2
ProjectName, Stratum
MC, Iteration
Timestep, Timestep
CTAbbr&":"&SSAbbr, State Class
Area, Area
Transition Summary:
3.1, 4.2
ProjectName, Stratum
MC, Iteration
Timestep, Timestep
TransGrpName, Transition Group
Area, Area
leonardo-fridKeymasterIf there is no need for spatially defining which cells the multipliers apply to, use the non-spatial multipliers. They are computationally more efficient.
Cheers,
Leonardo
leonardo-fridKeymasterWe have not tested ST-Sim on Windows 8 but there is no fundamental reason why it should not work. ST-Sim requires the .Net Framework 4.0 which should come with the Windows 8 OS.
leonardo-fridKeymasterAt the moment the only scenario property which is not compatible with running a simulation spatially is the non-spatial initial conditions property. All other properties including targets and multipliers are compatible with spatially explicit simulations.
leonardo-fridKeymasterTo our knowledge the largest spatial run on ST-Sim was for 21 million cells by researchers at NCSU so I believe that your simulations with 17 million cells should be possible. What may be happening is that you are running out of memory. I know that the NCSU folks had access to powerful computers with more than 21GB of RAM. Can you be more specific about the error you are getting when you attempt to load your sclass raster? You will also need to use the 64bit version of the application for this size of landscape.
leonardo-fridKeymasterThere are a number of different approaches that users have taken to document model metadata and there are some good examples in the model publications posted here:
http://wiki.pathmodel.com/index.php?title=Publications
Perhaps the project with the most thorough metadata documentation approach was the LANDFIRE vegetation dynamics models.
See: http://www.landfire.gov/downloadfile.php?file=UsingBpSDescrips_2009_03_25.pdf
leonardo-fridKeymasterHi Ayn,
Am happy to say that there is no longer a limit on the number of transition groups that a transition type can belong to.
Cheers,
Leonardo
leonardo-fridKeymasterHi Ayn,
1. The algorithm is the same as FRCC
2. Can you send me the database that is producing this error? I would like to see if I can reproduce it. Note that under File | Preferences you need to define which Attribute Group defines your strata.
Cheers,
Leonardo
March 25, 2013 at 6:55 pm in reply to: Randomize initial TSD within state specific range (VDDT #1817leonardo-fridKeymasterHi Max,
Yes, Path and ST-Sim both allow for loading initial conditions from excel. The limit would be the number of records possilbe on the version of excel you are working with so if you have excel 2007 or later that would be 1 million records.
Note that at the moment. TSD is not set for individual records in the initial conditions property for Path or ST-Sim. You can randomize TSD by stratum. In the future it is conceivable that your suggestion of randomizing by state class could be implemented or also the ability to specify TSD values for individual records in the initial conditions property. Note that in Path and ST-Sim TSD is referred to as Time Since Transition (TST).
Regards,
Leonardo
March 20, 2013 at 11:38 pm in reply to: Randomize initial TSD within state specific range (VDDT #1815leonardo-fridKeymasterHi Max,
In VDDT you can set TSD values by State Class for individual records in the Initial Conditions screen. This is described on page 62 of the VDDT user manual. If you want these values to be randomized you will need to do the randomization outside of VDDT and then create multiple records for each state class, each with different TSD values. At the moment we are no longer developing VDDT but the ability to randomize by state class could be an enhancement we consider in the future for Path / ST-Sim.
Regards,
Leonardo
-
AuthorPosts