Custom Query (1539 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 1539)

Ticket Resolution Summary Owner Reporter
#729 fixed csv from Ecosim all fit plot jeroens chiarap
Description

Ecopath version 6.1.0.0414 downloading the csv file from "Ecosim all fits" -- save plots the values i get for my "observed data or TS" are wrong.. much bigger that it should be

#145 fixed creating scenarios in Ecosim- using similar words causes problems administrator carieh
Description

When creating a new ecosim scenario, if I use the same word that have been previously used, the computer tries to guess what I am typing. For example in my model (Antarctic Peninsula) I named one of the ecosim scenarios carie, now if I try to name another one Carie Aug 9 after I type Carie it changes the words to carie (by un-capitalizing the C) and moving the cursor to the beginning of carie so basically this is annoying, but not a major bug. You can re-create by creating various scenarios with similar names.

#110 unable to duplicate creating and saving a new model- not working properly administrator carieh
Description

Creating a model, and saving it as lab 4 seal cod july 1.mdb

it doesnt like the name

Lab 4 sealcod july1 created.mdb or this name Lab 4 or this name Basically I dont think it likes any name I give it- I get this error (see word doc july 01 notes for screen images)

And the database doesnt create, or at least you would think. The model doesnt open right away. But If I then go back to open model I can click on the models that failed to open when I created them, and they open, same screen as a blank model. So it really did save, but it didnt open a blank model when it saved, you have to then go from create model, to open model and open the file you just created. It used to just open the model for you when you created a new database.A little annoying :-)

I cannot reproduce this error, although I know that the underlying logic does not properly handle overwriting an existing database. Situations to check:

  • The target DB is read-only
  • The target DB is in use
Note: See TracQuery for help on using queries.