|
What's New New in Version 3.80 May 2018 Under the View menu, you can find the "%Change Calculator" to compute the results of combining, compounding and reversing percentage changes. It can be very handy to work out shock values. More details here . RunDynam now has a new licence activation procedure, described at: www.copsmodels.com/gpactivation.htm A RunDynam 3.80 licence is required. There has been a big rewrite of the underlying code and many bugs have been fixed, so we hope you will find it to be more stable and smoother to use. The installer contains new versions of Tabmate, Viewhar, Viewsol and Analysge as well. Most likely these will be 64-bit programs (new for 2018). From within each program the Help -> What’s new menu item will describe new features. New in Version 3.70 You are now alerted, at the successful conclusion of a simulation, if any of the log files contained warnings. You get the chance to immediately see a summary of the warnings -- but you can see this summary later using the Warnings button on the results page (Dec 2016). Some changes in look and feel, especially in Dialogs selecting files and folders (Nov 2016). Under the File menu, there is a new command Clean up working directory which attempts to delete from the working directory all files produced during any Rundynam simulations. Use it to reduce the size of a RunDynam working folder prior to backing up, or to save disk space (Jan 2016). The ReLocDS program is very useful if you want to copy your entire project working folder (with sub-folders) to another location (Jan 2016). If you produce an HA File Showing Data File Values for All Years, RunDynam now stores the STI file used by CMBHAR in the working folder (previously was in a temporary folder). This means that you can use that STI file later to rerun CMBHAR (perhaps as part of a system of results processing) (Nov 2015). If you click on the label showing the model EXE (on the Model/Data page) you get some technical details about that file (March 2015). New in Version 3.66 (September 2013) When you restore Closure/Shocks files from a Closure/Shocks Zip Archive (or from a full Zip Archive), you will be asked which parts (if any) of the simulation details you wish to load. New in Version 3.65 (May 2013) RunDynam now remembers the window size and position you used in your last session. A small control at the extreme bottom right can be used to adjust font sizes to your preference. New in Version 3.62 (April 2011) When you use the menu item Load Closure, Shocks into AnalsyeGE in the Policy Shocks column on the Closure/Shocks page, if your model EXE is sufficiently recent, you will see as shocked variables which are exogenous in the Policy and endogenous in the Base. New in Version 3.61 (March 2011) If a simulation crashes, by default, RunDynam now does not stop immediately. Instead, RunDynam tries to complete as many parts of the job as it can. For example, suppose that you have asked to solve all years from 2010 to 2030 for Base, Rerun and Policy. If the Policy simulation for year 2015 crashes, RunDynam still tries to continue the Base and Rerun beyond 2015. You have the option of reverting to the old behaviour (stop immediately when there is an error) via menu item If sim job crashes? in the Run Preferences menu. There is a new menu item Write SEQ File for ViewSOL under the Tasks menu (just below item "Run SS Jobs for Selected Years"). If you have solved for several (but not all) periods of a scenario, you can use this to load the results (eg, of the Base) for those periods into ViewSOL. This may be helpful if your simulation crashes part way through the full scenario. There is a new menu item Load Closure, Shocks into AnalsyeGE in the popup menu when you right click on a cell in the Base or Policy Shocks column on the Closure/Shocks page. This loads the closure and shocks for that period of the Base or Policy into AnalyseGE. You may find that helps to understand the how relevant closure works. While a simulation is running, RunDynam now tells the operating system that the computer should not be put to sleep. New in Version 3.60 (March 2011) Version 3.60 includes the improvements of Versions 3.56 and 3.57 (which were only released to selected customers), and various small bug-fixes in ancillary programs such as ViewHAR, ViewSOL and the Charter. Also, Version 3.60 requires a new licence file (3.5x licences will not work). New in Version 3.57 (December 2010) It is now easy (though may be time consuming) to carry out Systematic Sensitivity Analysis (SSA) with respect to variations in parameters. The methods and the way results are reported are similar to SSA with RunGEM or RunGTAP. You can do SSA in batch mode. A bug in TABLO-generated programs and GEMSIM in Release 10.0-002 (April 2010) of GEMPACK meant that Managing MMNZ usually hurt rather than helped. RunDynam has been changed to work around this problem so that, even with that bug, Managing MMNZ now helps again. New in Version 3.56 (September 2010) RunDynam can now be used with quarterly or monthly models. These are models in which the lengths of periods are measured in quarters or months respectively. [Previously RunDynam only allowed yearly models, namely those in which the lengths of periods are measured in years.] You can use slice words <quarter>, <month> or <period> with these quarterly or monthly models when specifying shocks in BSH or PSH files. New in Version 3.53 (March 2010) RunDynam now usually requires a licence (which is different from your GEMPACK licence). If you have run a batch job, the next time you start RunDynam not in batch mode, the program will suggest you check the Batch Jobs Log File to see if the batch job succeeded. New in Version 3.51 (February 2010) There is a new group of scenario management items under the File menu. Here we use the term scenario as an alternative to simulation details. Creating a ZIP archive which does not include the model EXE has changed a little. This makes restoring from such a ZIP archive more effective. We give advice as to where you might work if you need to rebuild the model EXE. New in Version 3.50 (February 2010) You no longer need to provide the Model Information file (MIN file) for models which are prepared with Release 9 (or later) of GEMPACK. RunDynam can read the AXT or GST file directly when these have been produced by Release 9 or later of GEMPACK. New in Version 3.49 (January 2010) You can use integer offsets such as <year+1> and <year-2=ABC> when specifying the slice to read shocks from in BSH and PSH files. New in Version 3.45 (August 2009) RunDynam is able to manage MMNZ values used for simulations. This should speed up simulations in many cases. New in Version 3.43 (May 2009) We have made changes to: •where RunDynam offers to save Zip Archives and Closure/Shocks Zip Archives. •where RunDynam suggests looking for the Zip Archive or Closure/Shocks Zip Archive to restore from. RunDynam remembers where you last saved a Zip Archive and suggests the same place (folder) when you next save or restore from a Zip Archive. Similarly for Closure/Shocks Zip Archives. These is a new menu item Save Zip Archive and Restore in Same Place (under the Zip menu) which allows you to save a Zip Archive in a new directory and then immediately restore the files from the Zip Archive into this new directory. New in Version 3.41 (February 2009) You can now ask RunDynam to show you a combined file showing a logical file (one which relates to a Header Array file -- not a text file -- which is updated input or is output only) across all relevant years for any run (Base, Base Rerun or Policy). You do this by clicking on the All AHO item or the All CHO item (the last two items) in the right-hand list box in the Results for Individual Years on the Results page. New in Version 3.38 (November 2008) You can new delete all results via the menu item Delete All Results in the Results part of the Zip menu. This deletes those results files which would be zipped up if you selected menu item Zip up All Results under the Zip menu. New in Version 3.35 (September 2008) If you have selected an output file (one produced via Write statements in the TAB file) in the type of file box in the Results for Individual Years part of the Results page, what you will see when you click on the View button has changed. Now you will see the file produced during the simulation for the year you select. [Prior to Version 3.35 you would have seen the file produced during the simulation for the year one after the year selected.] We are grateful to Terrie Walmsley for pointing out the problems with the old treatment. New in Version 3.34 (September 2008) After you have run a Policy, it is possible to ask RunDynam to make this into a new Base case. Then you can investigate other policies starting from this new Base (that is, investigate other policies starting from the old Policy). This is done via the menu item Make Policy the Base under the File menu. New in Version 3.33 (August 2008) When you make a Zip Archive, if there are any files in the subdirectory EXTRA of your working directory, you are asked if you want to include all such files in the Zip Archive. [If so, these files to into EXTRA2.ZIP inside the Zip Archive. Subdirectories inside EXTRA are preserved there.] We are grateful to James Giesecke for suggesting this feature We believe that this will make it much easier for users to group together auxiliary files and to make sure that these files dont get lost when making a new Zip Archive. When you restore from a Zip Archive, all files in EXTRA2.ZIP are restored into subdirectory EXTRA (not EXTRA2) of the directory into which you are restoring the files. Again subdirectories are preserved inside EXTRA in that case. Perhaps confusingly (we do it for backwards compatibility), you are also asked (as before) if you wish to add some extra files to the Zip Archive. These can be taken from anywhere on the disk and go into EXTRA.ZIP in the Zip Archive. When you restore from a Zip Archive, files in EXTRA.ZIP also go into subdirectory EXTRA of the directory into which you are restoring (as before Version 3.33). New in Version 3.32 (July 2008) Several power users want to be able to run two or more versions of RunDynam in order to take advantage of PCs with several (4 or more) processors. They want to be able to use one copy of RunDynam to solve one dynamic simulation (Base and Policy) and to use another copy of RunDynam to solve a second dynamic simulation at the same time. Power users can look at details as to how we have accommodated this change. As developers, we (somewhat apprehensively) say yes to the power users who need this feature, and we tell those who try it that it is a case of User Beware. We strongly urge all others to keep to the simple and proven strategy of only running one copy of the EXE we supply. New in Earlier Versions Click here to see what was new in Version 1.4 (February 2000) to Version 3.30 (March 2008). URL of this topic: www.copsmodels.com/webhelp/rundynam/hc_whatsnew.htm Link to full GEMPACK Manual Link to GEMPACK homepage |