Distance 0 Beta 6 Release Notes 2 July 200

|
Distance 0 Beta 6 Release Notes 2 July 200
|
Sana | 24.12.2019 | Hajmi | 25,74 Kb. | | #4741 |
Distance 4.0 Beta 6
Release Notes - 2 July 2002
Contents
Installation Notes
Uninstalling Distance 4.0
Distance 4 beta discussion list - please read this section
Current restrictions for Beta 6
Known problems in Beta 6
New features and resolved problems in Beta 6
Appendix 1: Files Added During Installation
Installation Notes
System Requirements for Distance 4.0
Distance 4.0 requires about 35MB of space on your hard drive. Other than that, the practical minimum requirements are a computer with Pentium II Processor, 48MB RAM, 800x600 SVGA monitor with 256 colors running Windows 9x, ME, NT4 (Service Pack 3 or later), 2000 or XP. However, for satisfactory performance when using the GIS capabilities, we recommend having at least 64MB RAM with 128MB being much better. Some of the GIS operations are very computer intensive, so a modern processor gives significantly faster performance. Distance 4 also looks better at 1024*768 screen resolution, with more than 256 colors. However, for the pictures in the online help to display correctly, you need 32768 or more colors (“High color” or “True color” on Windows display properties).
Distance 4 help is in the next-generation Microsoft HTMP Help format. If you have Windows 98 or later then you will automatically have the necessary viewing software on your computer. However, if you have Windows 95 or NT4 then you may need to download the HTML help software from Microsoft. This software is installed automatically with Microsoft Office 2000 or Microsoft Internet Explorer 4.0 or later, but if you don't have either you should check after install that you can view the Distance help. If not, the easiest approach is to download and install the latest version of Internet Explorer (http://www.microsoft.com/ie). If you're allergic to Internet Explorer, you can probably install the HTML help viewer separately: go to http://www.microsoft.com and search for "HTML Help".
The Distance 4 User's Guide is also available in Adobe PDF format. To read this file (which is installed in the Distance4/Help directory), you need a copy of Adobe Acrobat reader, available from http://www.adobe.com.
Installing Distance 4
To launch the Distance 4 setup program, run the file d4setup.exe. You are then guided through the installation. If you have an older version of Windows 95, you may be asked to re-boot again early in the installation process and then restart the install. You may also be asked to reboot after install has finished.
Once Distance is installed, you can run Distance 4 from the Programs | Distance 4 folder off the Start menu on your windows Taskbar.
A list of the files added by Distance 4 installation is given in Appendix 1.
Installing Distance 4 alongside Distance 3.5
Distance 4 is designed to exist happily alongside Distance 3.5. By default it is installed into a different directory (C:\Program Files\Distance 4), and so will not overwrite any Distance 3.5 files. Distance 4 does not register itself to open .dst files, so Distance 3.5 will continue to open these files when you double-click on them. To open Distance 4 project files, you need to go into Distance 4 and choose File | Open from the menu bar.
Installing and Running Distance 4 on a network or multi-user system
To install Distance 4 over a network, you need to have appropriate permissions to write to the system directories. If you work in a large organization, you'll need to work with your network administrator to do this.
By default, Distance keeps its initialization settings in a file called DistIni.mdb, in the distance program directory. To run, it needs read/write access to this file. If the Distance program is placed in a directory where users do not have write access, then you will need to move this file, and tell Distance that you have moved it. You do this as follows:
(1) To create one DistIni.mdb for all users. Place the DistIni.mdb file in a folder where all users will have write permission. Edit the registry, and add a string key in
HKEY_LOCAL_MACHINE\Software\Distance\Distance 4.0\DefaultSettingsDbPath
The value should be the fully qualified folder name - e.g., if the file location is "X:\Users\AllUsers\DistIni.mdb" then the registry setting's value should be "X:\Users\AllUsers"
(2) To create a separate DistIni.mdb for all users. Place a copy of the DistIni.mdb file a separate folder for each user. Get the user to log on, edit the registry, and add a string key in
HKEY_CURRENT_USER\Software\Distance\Distance 4.0\DefaultSettingsDbPath
(You could also edit the appropriate location in HKEY_USERS.) The value should be the fully qualified folder name - e.g., if the file location is "X:\Sean\Distance\DistIni.mdb" then the registry setting's value should be "X:\Sean\Distance"
When Distance starts up, it will now use the DistIni file in its new location, rather than in the program directory.
Problems with Install
The following is a list of known problems with installing Distance. If you are having a problem that is not listed here, please (1) check your computer meets the minimum requirements (above); (2) check the archives of the Distance 4 beta discussion list (see section below); (3) look at the file c:\Program Files\Distance 4\Install.log to see if it gives you any clues as to the problem; (4) post a message on the Distance 4 beta discussion list.
Known problems:
Message “Files that are required for Windows to run properly have been replaced by unknown versions.” in Windows 2000. You may then be asked to insert the Windows 2000 CD, to have these files replaced by the original versions. If this happens in Beta 4 or later, please contact us as we'd like to know about it. (It is an example of a feature of Win2k called Windows File Protection. For more information, go to www.microsoft.com, click on support, and search for the articles Q236995 and Q222193. These show you how you can increase the size of the DLLCache on your hard drive, to avoid having to insert the CD in future when installing other programs.)
On many machines, you are asked to reboot during the install process. However, on some Win98 machines, during reboot, you get the message “Cannot find setup.exe”. Workarounds: 1. reboot again, or 2. Run d40setup.exe again.
Message "The procedure entry point __lc_collate_cp could not be located in MSVCRT.dll". This occurs under older operating systems because the version of the Microsoft C runtime library (MSVCRT) is out of date (version 5 or earlier). Solution: Reboot, and run setup program again. Setup program contains a new version, but a reboot is required for this new version to register.
Message "The dynamic link library urlmon.dll could not be found in the specified path". This occurs under older operating systems (has been seen on NT4) because urlmon and related files are not present. The file is currently required by one component of Distance (the ComponentOne Flexgrid). We are working on a permanent solution with the manufactureres of the component, but meanwhile a workaround is to install Internet Explorer 6.0 or later, and then run the setup program again.
Sample Projects
[no information at the moment]
Replacing the Sample Projects
To replace the sample projects, begin by deleting the old ones from the Sample Projects subdirectory of the Distance install directory (usually C:\Program Files\Distance 4). Then, re-run the setup program. In the "Select components" window, uncheck every option except "Sample projects". Continue through the setup program.
Uninstalling Distance 4
To uninstall Distance 4, click on the Add/Remove Programs icon in the Windows Control Panel. Choose Distance 4 from the list and click the Add/Remove button. During the removal process, you will be asked whether you want to remove shared components. Press "Yes to All". The install program may not be able to remove all of the folders under C:\Program Files\Distance 4\ if you have changed any files in them (e.g., by creating new projects in \Sample projects). In this case you will have to remove these folders manually after the installation has finished.
Distance makes no changes to the system registry, so there is nothing to delete there.
Distance 4 beta discussion list
We have created a new email discussion list for users of beta versions of Distance 4.0. One aim of the list is to allow you to give us suggestions and feedback, and for us to confirm problems and suggest work-arounds. Further, many of the new methods in Distance 4 are not yet in the published literature, and are only briefly documented in this manual. The new list allows you to ask questions about the new methods and get replies from the developers. (Please note that we can't guarantee to give comprehensive replies to all questions, but we'll do our best, within reason!) We're also interested to hear about your experiences with the new methods: what worked and what didn't.
We strongly recommend that users of this beta release join the list. To join, send an email to jiscmail@jiscmail.ac.uk with the following in the body of the message (not in the subject line):
join distance-sampling-d4beta yourfirstname yourlastname
Replace the text "yourfirstname" with your first name and the text "yourlastname" with your last name (e.g., join distance-sampling-d4beta Joan Smith)
In response, you will receive a message back that explains how to use the listserver. More information about the listserver, and an archive of messages sent to the list, are available at the list's home page
http://www.jiscmail.ac.uk/lists/distance-sampling-d4beta.html
Please check the archive of previous messages before posting!
Current restrictions for beta 6
· Project setup and import
o Multiplier fields are created in the database, but they are not automatically added to the default model definition - this applies to the cue rate multiplier too
o If length or distance fields are measured in one field but to be analyzed in another then only the measurement units are imported from the old D3.5 file. Units of analysis must be set in the new data filter manually. (This is because data filters are not imported when the project is imported, and analysis units are now in the data filters.) If the units are not one of those that Distance recognizes (from the default project settings database) then the units will not be imported.
· CDS and MCDS Analyses:
o Post-stratification by observation does not work for MCDS analyses - see known problem #84
· MCDS Analysis Engine
o Maximum 10 covariates
o Maximum 50 levels per factor covariate
o When covariates are specified, only half-normal and hazard-rate key functions allowed
o Cannot force the fitted function to be monotonic decreasing
o When cluster size is a covariate, stratified analyses are not allowed
o You cannot post-stratify by the observation layer [see known problem #84]
o Cannot have non-factor covariate value -9999.
Known problems in beta 6
The following is a list of known problems as of the release date. An up-to-date list will of problems and work-arounds will be kept at the Distance web site (http://www.ruwpa.st-and.ac.uk/distance/), and work-around will be discussed on the Distance 4 beta discussion list.
Resolved problems and new features in beta 6
New Features
· Main form: Each child form now has a context-sensitive menu item on the main toolbar.
· General: Most windows now have a copy button on their context-sensitive menu, which copies the contents of the window to the Windows clipboard. There is also a “copy current window to clipboard” button on the main toolbar.
· MCDS Engine: Can now estimate detection function at multiple levels, by ticking more than one level for detection function under “Quantities to Estimate” on the Estimate tab. Why is this useful? For example, imagine you want to estimate density by stratum, but don’t have enough data to fit a separate detection function for each stratum. Select the MCDS engine. Tick the density global and by stratum boxes. Then tick the detection function global and by stratum boxes. Add Stratum ID as a factor covariate. Then Distance will model detection function at the global level, but will estimate a separate detection function by stratum (using the global model, but the stratum covariates), and will use the stratum level estimate of f(0) (or h(0) for point transects) to estimate density at the stratum level. A restriction is that variance of density at the global level must be estimated via the bootstrap. This functionality is currently undocumented, but will be documented for the next release.
· MCDS Engine: Maximum number of factor levels increased from 20 to 50. Stack size increased to 100MB to cope with large data sets.
· CDS and MCDS Engine: Satterthwaite degrees of freedom no longer rounded to nearest integer (see Distance book for details of Satterthwaite correction). This means degrees of freedom for density, abundance, etc can be non-integer, and the calculated confidence intervals on these quantities will be slightly different from (i.e., more accurate than) previous versions.
· CDS and MCDS Engine: When right truncating by a percentage of the data, or by the largest distance, Distance formally truncated each component of the analysis separately according to the level of estimation chosen (e.g., detection function by stratum meant different truncations in different strata). See known problem 168. This has been changed so that truncation is now done globally, and is the same for all components of estimation and all strata.
· CDS and MCDS Engine: Stats file output now to 7 significant figures (was previously only 5). This is most useful for output such as AIC where the least significant digits are often the most important. Also, degrees of freedom are now output as real, rather than integer. The new FORTRAN format statement is FORMAT(1X,I3,1X,I3,1X,3(I1,1X),G14.7,1X,F7.4,1X,2(G14.7,1X),F14.7)
[old one was FORMAT(1X,I3,1X,I3,1X,3(I1,1X),G12.5,1X,F7.4,1X,2(G12.5,1X),I5)]. Note that this means any routines written by users that read the stats file will need adjusting.
· Data Filter Properties: Added ability to right truncate a percentage of the data for interval as well as exact data, so long as the intervals are set manually. For interval data, the truncation point is chosed so as to discard at most the given percentage of the data.
Components: PolarZip.ocx upgraded from 5.0.5.2 to 5.0.12.0. This fixes various minor bugs in project file import/export.
Components: vsFlex7d.ocx upgraded from 7.0.0.78 to 7.0.1.151. This allows us to implement fixes some bugs in the grids - e.g., #s 30, 172, etc.
Components: Actbar2.ocx upgraded from 2.0.1.1073 to 2.5.0.32. Fixes many bugs in the toolbar, and allows for context-sensitive menu.
Map Browser: Map preview pane completed - under click on “Show Preview Pane” to start.
Resolved problems
Interface
{132} Analysis Browser: Can set the set name to "" (by pressing delete on set name, then enter), in which case you can't then select that set again. Need some check that set names are valid before they are changed. Could also possibly do with a confirm set name change dialog box. [18 Sept 01, LJT]
{163} Analysis Browser: On Windows XP, get an “invalid property” error from CCtlBrowser.FormatNameGrid when Distance tries to open the Design, Survey or Analysis Browser. [This is caused by a bug in WIndows XP, which is due to be addressed in XP Service pack 1. As a temporary fix, I have installed an extra component comctl32.ocx - this makes the install file bigger, but works okay. When XPSp1 is released, I’ll go back to the old way of doing it.] [18 Jan 02; fix updated 17 April 02 LJT]
{177} Analysis Components: can inadventently rename items to be blank, by highlighting the set name, pressing delete and then enter. [11 Apr 02, Aaron Ellingson, LJT; Fixed 30 April LJT]
{173} Analysis Details, Inputs tab. When there are enough data filters or model definitions to exceed the window length, it can be hard to select a particular one. Clicking on one results in the highlighting skipping to an adjacent definition. Often, the only way to get the definition I want is to use the arrow keys. [11 April 02, Aaron Ellington & LJT; Fixed 24 April 02, LJT]
{172} Browsers: when the right pane has a horizontal and vertical scroll bar, the two panes can get out of synch when you scroll down to the bottom item [Fixed 24 April 02, LJT]
{176} Browsers: can inadventently rename sets to be blank, by highlighting the set name, pressing delete and then enter. [11 Apr 02, Aaron Ellingson, LJT; Fixed 30 April LJT]
{186} Browsers: flicker too much as status changes when running items [Fixed 2 July 2002 LJT]
{30} Data Explorer: Header often gets out of synch with the lower grid - this particularly happens when the lower grid has a scroll bar and you scroll to the right-hand end of the grid, forcing the lower grid to scroll - the top one does not scroll along [Internal note: the problem is in flxDataSheet_AfterScroll: the statement flxDataSheetHeader.LeftCol = flxDataSheet.LeftCol has no effect - need to alert VideoSoft.] [Fixed via a work-around LJT 24 April 02]
{34} Data Explorer: Creating a new Coverage layer, if the layer is stored as projected (e.g., Plate Caree in the Mexico sample project) then you get a Type Mismatch error (13) in Distance.ClsGrid.MakeGridProjection [8 Feb 01 Sam; Fixed 17 June 02, Len]
{181} Data Explorer: Creating a new Covarage layer, if you press Cancel when Distance tells you how many points are going to be added, a layer is created anyway (but with no points in it). [Fixed 17 June 02, Len]
{174} Data Explorer, Data Layer Properties Dialog. Change coordinate system dialog box not disabled when the layer is not geographic. [29 April 02, LJT; fixed 29 April 02, LJT]
{175} Data Explorer: Copying data to clipboard is slow. [Fixed 29 April 02, LJT]
{137} Data Import: Cannot import rows with missing values in some columns. Would be better if it put out a warning, but imported anyway with field being set to Null. [1 Oct 01, Len]
{180} Data Import: Under some circumstances, doesn’t import the first row of data, and no warning message generated [25 May 02, Louise Burt; Fixed 5 June 02, Len]
{178} Details Inputs and Log: The comments window creeps up the form each time it is loaded. [Fixed LJT 11 June 02]
{160} Model Definition Properties: Once you have selected a field for the Multiplier SE, you cannot then select no field [LJT 4 January 2002; fixed LJT 4 January 2002]
{182} Setup Project Wizard: When using current project as template, no global record is created, so the data import wizard doesn’t work. [Steve Fancy 11 June 02; Fixed LJT 18 June 02]
Analysis Engines
· {161} When multipliers divide the density estimate, the value of the SE is calculated incorrectly [2 Jan 02, Dan Pike; Fixed 7 Jan 02 Len]
· {165} If an output file (e.g., results file) is specified in the Model Definition, but the directory does not exist, then the Analysis Engine quits without any explanatory error message. [15 Feb 02, Amaia Gomez; Fixed 15 Feb 02 Len - the interface now checks that the directory exists before running the analysis engine, and if not puts out an error message]
MCDS Analysis Engine
{159} AIC, BIC, etc values in the Analysis Browser have lost their decimal places. [19 Dec 01, LJT. Fixed 22 Dec 01 - output in stats file given 2 more decimal places. This will still occur for some large values of AIC however.]
{166} Cluster size regression expected cluster size calculated wrong, when g(x) is the independent variable. [15 Feb 02, LJT; Fixed 15 Feb 02, LJT]
{167} Can crash on bootstrap analyses with array bounds exceeded error [15 Feb 02, Dan Pike; Fixed 16 Feb 02 Fernanda]
· {168} If you use more than one key function, and the second has more parameters than the first, can get a crash in Labels.for with array out of bounds [18 Feb 02, LJT; Fixed 20 Feb 02 Fernanda]
· {169} When right truncation of a percentage of data is chosen or no truncation (ie truncation by largest distance), the truncation is done separately for each component of estimation (detection function, cluster size and encounter rate), and is done at the chosen level of estimation (e.g., globally, by stratum or sample). This means that if you choose different levels of estimation for different components, you get different trunctions - e.g., detection function by stratum yields different truncations for each stratum, and cluster size globally yields yet another trunction for cluster size. This also means that AIC for stratified and non-stratified analyses are generally not comparable. [21 Feb 02, LJT & Louise Burt; Fixed 21 Feb LJT: truncation in these cases is now done globally]
· {170} Hi resolution example detection functions not plotted in some cases. In the plot file, the function evaluations are all negative. [23 April 02, LJT; Fixed 23 April 02, LJT]
· {171} Certain covariate names (Distance, Angle, Size, those starting with STR_ or SMP_) cause the data preparation part of the MCDS interface to fail. [11 April 02, Aaron Ellingson and LJT; Fixed 23 April 02, LJT - covariates with these names are renamed by data preparation component, and a message put in the Log file]
· {183} When specifying more than one detection function model, get Internal Error 23, and incorrect results reported. [11 April 02 Aaron Ellingson and LJT; Fixed 19 June 02 LJT]
Appendix 1: Files added during Distance 4 Installation
Note - if older versions of these files are already present, they will be overwritten. If newer versions are already present, they will not be changed. (An exception to this is RichEd32.dll, which caused some incompatibility problems in test installations. This file will only be installed if one is not present on the target system.) If you selected the backup option during Setup, backups of all overwritten files will be stored in the BACKUP subdirectory, off the Distance 4 program directory.
[packing list not available for beta version]
|
| |