Custom Query (1539 matches)
Results (100 - 102 of 1539)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #984 | not an issue | Ecosim screen vs results mismatch | cathyb | |
| Description |
Here is example of that bug; the first image shows really minor differences: the Seal group relative change in the Results tab shows 1.407610 (presumably end of year 49) while the Ecosim plot tag shows 1.487181 at 2043. The Basic Estimates tab (which you don’t have a shot of ) show seal starting biomass as 0.0408 and the Ecosim Results tab shows it as 0.043101 (but ok difference if Ecosim start one month after zero). If you divide the end biomass i.e. 0.060669 by the Basic estimates zero starting mass you get 1.486985 (closer to the screen tag 1.487181 than to the Results E/S of 1.407610). Ok these are really tiny but it would be good to know exactly at what point these values are taken for these calculations and make sure they are consistent. (Perhaps I need to read the manual J). But here, image 2, is an example of things going haywire where those differences are much larger and potentially misleading. Whiting on the Ecosim screen tag and the screen plot itself apparently increases x66.87299 but the Ecosim Results s/s says only 5.140508. Here you can see a really big difference in the starting biomass of the Ecosim Results tab 17.813709 cf the basic estimates tab 1.369305. This would cause me grief if, as I usually do, cut and paste the Ecosim results without checking absolutely although I know if they are really off as these are. But then I try not to get haywire results such as theseJ. But you can see what I mean about mismatches now. I hope J. My take on this would be that your starting point is your starting point i.e. before you start cranking anything and pretty much as the screen display shows. An issue of which value to use I think and maybe this has always been the case and that my models are so well-behaved that I haven’t noticed the difference before. Huh if only. |
|||
| #992 | fixed | Multiple Runs option should be more accessible | jeroens | |
| Description |
The Run Ecosim > Multiple runs option is buried in the options menu. It is too hard to find now. Instead, it should be accessible right on the graph toolbar. |
|||
| #994 | fixed | Cannot Delete Groups in Ecopath 6.2 beta | keithhg | |
| Description |
I am trying to delete a group in Ecopath 6.2 beta, when I click OK the group does not delete and then windows gives me a warning and the program crashes. Not sure what is going on. Below are the details of the Windows warning:::: See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. Exception Text System.NullReferenceException?: Object reference not set to an instance of an object.
Loaded Assemblies mscorlib
EwE6
Microsoft.VisualBasic?
System
System.Windows.Forms
System.Drawing
System.Runtime.Remoting
EwECore
EwEUtils
EwEPlugin
WeifenLuo?.WinFormsUI.Docking
SourceGrid2
System.Configuration
System.Xml
_avp9fad
SAUPUtil
System.Data
EwEFlowDiagramPlugin
EwENetworkAnalysis
System.Web.Services
EwEResultsExtractorPlugin
axvgq9pv
System.Web
Microsoft.mshtml
System.Transactions
System.EnterpriseServices?
System.Deployment
JIT Debugging To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration>
</configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. |
|||
