Distance 1 Release 2 Release Notes

|
Distance 1 Release 2 Release Notes
|
bet | 1/2 | Sana | 24.12.2019 | Hajmi | 54,05 Kb. | | #4740 |
Distance 4.1 Release 2
Release Notes - 2 December 2003
Contents
Installation Notes
Upgrading from previous releases of Distance 4
Uninstalling Distance 4.1
Distance-sampling email list
Current restrictions for Release 2
Known problems in Release 2
New features and resolved problems in Release 2
New features and resolved problems in Release 1
Appendix 1: Files Added During Installation
Installation Notes
System Requirements for Distance 4.1
Distance 4.1 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 (see below for other operating systems). 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.
Running Distance 4 under other operating systems
To run Distance under non-Windows operating systems, a Windows emulator is required.
Linux: Although we don't have any direct experience, Distance should run without problems within the emulation software VMWare (http://www.vmware.com) or win4lin (http://www.netraverse.com/). If you try this, please let us know how you get on!
Apple Macintosh: Distance 4 was tested on a G4 PowerMac running Virtual PC (http://www.connectix.com/) and ran without problems, although it required a fair amount of memory and runs quite slow.
Running Distance in extended character systems
If you use an extended character operating system (e.g., Chinese, Japanese or Korean language Windows) then you need to make the following change to the program preferences before you start using the program. Once you have installed Distance:
1. Start Distance
2. From the menu, choose Tools | Preferences...
3. Click on the General tab. Un-tick the box "Store results in compressed format in project databases"
4. Click OK.
You need to make this change because by default Distance compresses the results from analyses when it stores them in project databases, and at present it cannot decode these results on extended character operating systems. For more information, see Known Problem 247 (on the Distance web site, support page).
Installing Distance 4 under Windows
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 registers itself to open .dst files, so you'll have to open Distance 3.5 project from inside Distance 3.5.
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.1\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.1\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 list of know problems on the distance web site; (2) check the archives of the distance-sampling discussion list (see below); (4) look at the file c:\Program Files\Distance 4\Install.log to see if it gives you any clues as to the problem; (5) post a message on the distance-sampling 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.
Message "Distance could not find a component it requires to run". This has been known to occur on a Windows 2000 Server, but may occur on other systems. On that machine it happened because the database component (Microsoft DAO 3.51) was corrupted. The solution was to install some additional database software from Microsoft (MDAC 2.0). The program authors have a copy of the install package required -- please contact them for details.
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.
Upgrading from previous releases of Distance 4
To upgrade from a previous release of Distance 4, simply install the new version over the top of the old one. If you want to keep the same projects, you should rename them first.
After viewing some model definitions created in Distance 4.0 Release 1 in the Model Definition Properties (for example analyses that use smearing), you get the warning dialog telling you that a model definition has changed and that results for the analyses will need to be reset. This is because some formatting in the way model definitions are stored has been changed (to fix to problem 210). You'll have to run the analyses again but the results should be unchanged.
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-sampling email discussion list
The purpose of this list is to promote the sharing of ideas and information among researchers and practitioners interested in distance sampling techniques. It is a relatively low-volume list, and has been running since 1998.
Suitable topics for posting include: questions about survey design and analysis, new methodological developments ,use of software tools (program Distance and other software) ,news about upcoming meetings, workshops and conferences where distance methods will be discussed ,jobs in distance sampling-related fields .
To join this distance-sampling list, 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 yourfirstname yourlastname
Replace the text “yourfirstname” with your first name and the text “yourlastname” with your last name (e.g., join distance-sampling 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.html
Please check the archive of previous messages before posting!
Current restrictions for Release 2
· Project setup and import
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 number of covariates and factor levels is listed in the manual, under “Limitations”
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 Release 2
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/).
Installation
{96} 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. [Len: 13 March 01]
{179} On vanilla Win NT 4.0 SP6 machines (and possibly others), during the last part of the install, you get the error message "The procedure entry point _lc_collate_cp could not be loaded in the dynamic link library MSVCRT.dll". After installation is completed, you then cannot load geographic projects into D4 (e.g., the sample project D4Mexico). Workaround: reboot, then install Distance 4 again. [Len 10 May 2002 - cause new version of MSVCRT is installed, but is not backwards compatible -- need to find some way to reboot before registering components if MSVCRT is replaced]
{246} One user reported the following on an XP machine. The first time they created a project, Distance a run-time error message: “Automation error. Library not registered.” the source of the error was reported as D4Unit.StringHandling.LocaleDepDec. Solution: (i) Uninstall Distance; (ii) Download and install Windows Script 5.6 from the scripting page of the Microsoft Web site, which is currently www.microsoft.com/scripting; (iii) Reboot; (iv) Re-install Distance. (Note: Windows Script 5.6 is supposed to be shipped with Windows XP but it may be that another program on this person’s system had broken it). [Colin Driscoll 24 Oct 03; Workaround LJT 27 Oct 03]
Interface
(Design properties items are in the next section, with the Design Engine)
{16} General: Interface doesn't prevent user from making changes while items are running – e.g., changing the Data Filter or Model Definition while an analysis is running. If you do this, however, you will get errors.
{194} General: When upgrading from a Distance 3.5 project, and the destination folder for the D4 project is different from the source folder of the D35 project, under Windows 98 get an error that the new data file cannot be opened. This error doesn’t occur under Windows XP. [Len 5 Aug 02]
{195} General – properties windows. When you press F1, the help window that opens is always the same, regardless of which tab is showing. Ideally, the help window would be appropriate for the tab. [Len 12 Aug 02 – Cause: couldn’t get the Control Extender’s generic event to fire when late binding the properties controls – would like to have an event called HelpContextIDChanged that passes a new contextID each time a tab is shown in the properties controls. Perhaps to do with binary compatibility?]
{247} General – Details windows. On systems with extended character sets (e.g., Chinese, Japanese and Korean Language systems), the results of running analyses, surveys, etc. are not displayed. This occurs because the results are compressed in the project database and the decompression doesn’t work on these systems. Workaround: choose Tools | Preferences, and under the General tab, un-check the box “Store results in compressed format in project databases”. Now analyses you run should display fine. Note that you will have to re-run previous analyses for them to display. If you exchange projects with computers that do not have extended character systems, these computers will have to have the compress option switched off too. [LJT 28 Nov 2003]
{19} Analysis Components: "No item selected" message sometimes pops up when you try to delete a Data Filter or Model Definition, even if you know that one is selected. Workaround: Close the window and re-open it. [Internal note: Caused by bug in grid component where the grid is not binding tightly enough to the data control, and the record gets out of synch. Need to contact VideoSoft for fix or find a workaround.]
{21} Analysis Details, Results tab. When the results page titles are very long, the drop-down combo list gets resized so it is wider than the screen, and so the scroll bar disappears. (Note: Problem is in D4Util.ComboAdjustWidth – need to use an API routine to get the left pixel position of the drop-down and subtract this from the screen width.) [1 Dec 00]
{134} Analysis Details, Results tab. When results pages are very long, and you scroll down to the bottom of one page, then when you click on next you are taken to the bottom of the next page. Should take you to the top of each page as you enter it [26 Sept 01, LJT]
{226} Analysis Details, Results tab. When pasting a graph into another application that had been copied from CDS or MCDS results using “copy plot to clipboard”, one Windows ME system intermittently gave the error message “Distance has caused an error in MSCHRT20.ocx”. Workarounds – (1) seems to be less common if you leave the graph page showing while doing the paste (ie don’t close the Analysis Details window); (2) save the plot data to file in Model Definition | Detection function | Diagnostics, and use the macro on the Distance web site from Tim Gerrodette to reproduce the plot in Excel. Note – this is a problem with Microsoft’s chart control and we don’t expect to be able to fix it. Related to known problems on the Microsoft web site support page numbers 139577, 142793 and 179458. [Rob Williams 31 March 03].
{22} Browsers/Analysis Components: When you delete a Model Definition in the Analysis Components window, the IDs of the model definitions are not updated in the Analysis Browser table. [2 Nov 00] Also happens when you delete an analysis set using the Analysis Browser toolbar – the IDs of the new set shown are not updated. This causes an error in the mouse over event of the Analysis Browser when it doesn't recognize the ID – should error trap this, as well as fixing the source of the problem. [3 Nov 00]
{24} Browsers: Results pane (right hand side) – results with many 000s (either large or small) are not displaying in exponent format.
{25} Browsers: when you hit Enter after changing the name of an item, all items in that set become selected (only the one you were editing should be selected).
{26} Data Explorer: When you delete a data layer, any open design and survey details results windows that display maps go blank. [12 Jan 01]
{28} Data Explorer. Some data editing functions missing: when you hit tab in data entry mode you are not taken to the next cell; the up and down arrow keys move you along the edit string rather than up and down. Probably more issues here.
{29} Data Explorer: Operations that alter the structure of the data base (adding or deleting data layers, adding or deleting data fields, renaming fields or layers) cause an error if the data sheet is already locked by something else – for example if the layer is in a map that is open, or a design run. [Len: I need to go through the data sheet code putting in LockDataLayers method calls, and also need to enforce no editing of data while items are running.]
{31} Data Explorer: When you add a new field to an existing data layer, the values are blank and have no default. [I don't know what's a sensible thing to do here...]
{32} Data Explorer, Shape Properties. When you input an invalid shape (e.g., only one vertex of a polygon) you get no warning messge – the shape is simply not saved.
{133} Data Explorer - there is no way to delete cell values. Pressing Del should turn the value into a Null - useful, for example, if you want to represent missing data in the data sheet (e.g., missing covariate values). [26 Sept 01, Len]
{138} Data Explorer, Data Import, etc. Currently, there is no check that a field name is valid (e.g., in renaming fields, in importing new fields, etc). [1 Oct 01, Len]
{36} Data Filter Properties, Units tab. When you specify units other than "Same as...", you can get warning messages about overwriting the defaults when you run the analysis.
{129} Data Filter Properties, Units tab. Angle is automatically specified as Degrees here, but unless you also specify some valid angle units in the Data Explorer, you get an error message when running the analysis: "The angle field 'Angle' has no units associated with it." This message is unclear - should say where you need to specify the units. [10 Sept 01, Len]
{37} Design Browser and Details: When you run a design to generate a coverage probability grid, if you say OK to overwrite an existing field, if it fails, it leaves the data layer in a poor state (the field name is deleted from DataFields but the field is still in the data table).
{38} Design Details: There is no "Stop" button once you press run. [12 Jan 01]
{39} Design Details: You can change the Type Of Design for designs that have been run, or that have Surveys attached to them, without Distance noticing and prompting you to agree to reset the Design and Surveys. [14 Jan 01]
{42} Details Windows: Too much refreshing and flickering of combo boxes when new items selected. Particularly bad in Analysis Details.
{45} Details Log Windows: Clicking on an error in the bottom window doesn’t scroll you to that line in the top window.
{211} Import Data Wizard: “Error 3433: Invalid setting in Excel key of the Engines section of the Windows Registry” on some machines, when you click Next to go from the Data Destination step to the Data File Format step. This is not a bug in Distance; another program on the affected system has changed a part of the windows registry to a state that isn’t valid. The solution is to edit the windows registry to correct the problem. To start the registry editor program, click Start and then Run. In the Open box, type Regedit.exe. In the registry editor, expand the following key: “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\3.5\Engines\Text”. Under the Format key, you should see the following value: Delimited(). From the menu choose Edit and then Modify and change the value to CSVDelimited. This should fix the problem. If not, or the value was already CSVDelimited, then you have a different problem. [DLB 14 Jan 03; Solution LJT 15 Jan 03]
{222} Import Data Wizard: Importing large datasets is very slow. [20 March 03]
{46} Main Window: If you stop a design simulation mid-way through (by pressing Stop on the toolbar), the progress % indicator on the main toolbar still says Progress x% - this should be cleared. Perhaps the design is not halted correctly or completely? [12 Jan 01]
{47} Map Browser: Doesn't allow you to hit enter in the name field in browser grids while editing.
{48} Map Browser: Sometimes when you try to delete a stored map, it claims that "No map selected" when you can see that one is [Internal note: this is a problem with the data control not being on the same record as the flexgrid – see CCtlMapBrowser.DeleteMap]
{184} Map Window: If you use map tips, then when you try to close a project, get a message that it could not compact the project as DB still in use. Possible reference leak in map tips? Message goes away once you’ve exited Distance. [25 June 2002, LJT]
{49} Model Definition Properties: CDS and MCDS – Multipliers tabs. If you select the CueRate box for any other than the first line in Multipliers, Distance will put them on the first line next time you open the properties
{125} Model Definition Properties: MCDS. You can get to the position when it thinks cluster size has been added as a covariate when it hasn’t. To get there: add a covariate, tick the cluster size box, then remove the covariate. Clicking on the first tab, shows it thinks cluster size is a covar. [LJT 19 July 2001]
{50} Properties: When you click on OK, the contents of the current tab are not validated before the contents are saved [7 Dec 00]
{51} Preferences: Changing options do not seem to have any affect until you restart (e.g., changing default open path; changing timestamp and echo data options for analysis).
{52} Survey Properties, Data Fields tab. Not updating properly when survey methods options chosen. (For example, change from line transect to point transect, the perp distance field is still white and the radial distance field greyed out, rather than visa versa).
{53} Survey Properties: When you change the properties of a survey that has status run, the status is not reset or results deleted [12 Jan 01]
Design Engine and Design Properties
{40} Design Properties: When you change the properties of a design that has already been run (ie coverage probability results exist), the status is not reset or results deleted [12 Jan 01]
{41} Design Properties: Pressing Defaults causes an object not found error.
{55} Design Engine cannot be run out of process (possibly some problem in the NEngineInterface) – gives a "cannot find stratum" error (by "run" I mean generate surveys and assess probability of coverage) [15 Jan 01]
{87} Design Properties: Problem with the calculator for probability of coverage when it is assumed even. See 87.zip -- BajaCalifornia Norte has 87% of the effort, but looking at the results of the probability of coverage it is 0 for almost all the strata except the Sonora one (see Map and Grid1 field New Design). [9 Feb 01, Len]
{88} Design Properties: Zigzag design, maybe others. Tick allocate effort by sampler length, update effort in real time, percentage from __ sampler length. Now, as you enter values in the sampler length, you get error messages saying that the amount is not enough – I don't think it should check as you actually change the number, but only when you loose focus from that box. [9 Feb 01, Len]
{89} Design Properties: Crash in design engine – subscript out of range. See New Survey in 89a.zip. See also 89b.zip – may be the same problem, or a different one. I think in this case it is something to do with the rotation of the design axis for each stratum – when I set them all to 0 it runs no problem. [9 Feb 01, Len]
{90} Design Properties: Equal spacing zigzag, Effort allocation, Design axis section. The Defined as geographic coordinates tick box is enabled when you start by default. If you click on the radio button Determined by start and end location, and then back on Runs at angle to design axis it is now disabled and I can't seem to re-enable it. [9 Feb 01, Len]
{91} I don't know if the error messages in the survey for 91.zip are valid nor not – 1,000,000 meters of sampling seems like it should be enough (see last bug for why its not in kilometers!). Looking at the data sheet, it does seem to have created 2 lines. When I try 1,000,000 meters of effort per stratum, I get lines generated too, but also the same error messages in each stratum. [9 Feb 01, Len]
{92} Incorrect error messages about lines being too long and reset to 100000 in 92.zip [9 Feb 01, Len]
{103} Sampler properties are not saved properly if you don’t choose same properties for all strata. This can cause various error messages when running the design or survey, e.g.: (i) No effort, unable to generate survey; (ii) Error 13 (type mismatch) in D4DesEng. ControlDesignProcess. ReadDesignDefinitionString. To reproduce: (i) Open mexico sample project; (ii) create a new design; (iii) on General Properties tab choose Stratum Layer: “MexStrat”; (iv) on Sampler tab, uncheck Same Properties for all strata; (v) click OK to save the sampler properties; (vi) open the properties again, and go to the Sampler tab – the properties for all the strata except the first one are now blank. [20 March 01, Len]
{120} If don’t define polygon for global stratum, then plots of surveys and designs at the region level have a strange extent [18 June 01, David] [Len to fix].
{121} Get an error message when you run designs with new layer names that include a “.” or “_”. [18 June 01, David] [Len to fix]
{122} Adjusted angle design sometimes plots both a straight line and a curved line for some sections of some transects (at least I’ve seen it do it on at least one transect quite frequently). See survey IJHalf2 (and IJHalf1) in 122.zip. [18 June 01, David]
{123} When using a design to create a new survey, the area and effort field names are not filled in (they are shown as [None] in the Survey Properties | Data fields tab. (Internal note: the relevant commands are the Fld part of Area /Lyr= /Fld= and Effort /Lyr= /Fld=). [11 July 01, Len]
Analysis Engines
· {130} When running an analysis, if units are of the wrong type (e.g., angle field has units "meters", then the resulting error message isn't very helpful: " Internal Error description: "Error reading project or program setting 'AngUnit.Metre': Setting not found, and no default supplied." [10 Sept 01, Len]
· {190} When you specify starting values or bounds on parameters, doesn’t check that the number of starting values does not exceed the number of parameters, and that the number of bounds does not exceed the total number of key functions. (Note – see engine code commented out routine CheckBounds for more info). [LJT 17 July 02]
· {227} On some machines (Windows 2000 and XP only) where the user has a name with accents in it, running any analysis produces the following error message:
** Warning: Analysis engine wrote some output to the console error stream, reproduced below. **
-- Start of Console Error Stream --
forrtl: severe (43): file name specification error, unit 13, file [there may be a file name or some jibberish here]
Image PC Routine Line Source
D4.exe 004B0039 Unknown Unknown Unknown
[other lines here deleted]
D4.exe 00431155 CLRDAT 937 Datcom.for
The problem is that the FORTRAN analysis engine is not able to cope with TEMP directories that have accents in them. The solution is to rename your TEMP and TMP environment variables. Instructions for Windows XP (something similar should work in other operating systems): (i) Using Windows explorer, create a temp directory e.g., C:\Windows\Temp (or you may have one there already; you can use any other folder you like so long as it doesn’t have an accent in the folder name) (ii) From the control panel, open System Properties; (iii) In the Advanced tab, click on Environment variables; (iv) In the top window, look for the user variables TEMP and TMP. If they are there, change them both to c:\Windows\Temp (click the EDIT button). If they are not there, don't worry; (v) In the bottom windows, look again for TEMP and TMP. If they are there, change them both to c:\Windows\temp. If they are not there, click on New to create them (one with variable name TEMP and value c:\Windows\Temp, then another with variable name TMP and value c:\Windows\temp); (vi) click OK to confirm the changes and then reboot to get the new environment variables loaded. The analyses should now run without problems. Contact us if it doesn’t. [LJT 14 April 2003; workaround 20 Oct 2003]
· {236} When running an analysis, occasionally get an error from D3NEH.NEngineHost.OpenProjectDatabase. Error number 3260, “Couldn’t update; the database is currently locked by user ‘admin’.”, source D4DbEng.ProjectSettings.Setting. Currently only reported on a Windows 2000 machine. [Charles Paxton 9 May 2003] [I think I’ve fixed this, but will leave as outstanding until confirmed, LJT 9 May 2003]
CDS Analysis Engine
· No known problems
MCDS Analysis Engine
{66} Slow. Generally needs some tuning of estimation. (Can vectorize arrays, etc.) [Aug 2000]
{157} GOF P-value not saved to stats file [4 Dec 01, LJT]
{162} Bootstrap CV and confidence limit estimates do not include variance due to multipliers. This means that the bootstrap results underestimate variance when multipliers with SEs>0 are specified. [9 Jan 02, LJT]
{198} On Windows 2000, MCDS example detection function plots do not display properly – they show as two lines (red and blue) and no figure, rather than the expected 3 lines (yellow, orange, red) Solution: Install Windows Script 5.6, available for download from Microsoft (www.microsoft.com/scripting) or from the Support page of the Distance web site. [18 Aug 02, LJT]
{217} Smearing has not been tested for the MCDS engine – it may produce incorrect results. In any case, qq-plots for MCDS analyses with smearing have been disabled, as they don’t make sense when there are non-integer numbers of observations. [LJT: 3 Feb 03]
Resolved problems and new features in Release 2
|
| |