Publish from Vensim fails - VPM file has no data

[ajclarke]

I have a Vensim DSS model and clicked on PUBLISh but the window that appears does not allow me to select TOOLSET as it is greyed out.
What am I doing wrong?
My Vensim is version 5.9e

[Wilson]

AJ, I moved your post to the Vensim section.

I can't think of a reason why the toolset option would be unavailable. Normally the tool set option is only greyed out if you are using PLE/PLE PLus. Have you previously had PLE installed on your computer ?

At the bottom of the Publish dialogue box in the section for "problem solving details", does it say something like ....

Vensim® DSS for Windows Version 5.9e

Is the "settings" check box also unavailable ?

[ajclarke]

Yes I did have PLE installed but I ununstalled it bfore installing DSS.

Bottom of window has a box that says:
Vensim® DSS for Windows Version 5.9e Serial #2919001 Windows NT/2K/XP Version 6.1 build 7600

Also the Settings option is available and ticked.

So what do I need to do to remove the thing PLE has left behind? ( I uninstalled it and the Vensim Reader and reinstalled DSS but no better.)

[Wilson]

AJ,

The PLE thing is probably just a coincidence, but it was the only piece of information I could see in the manual as to why the toolset check box would be unavailable.

I'm sure when either Bob or Tony see your posting they will know immediately where the problem lies. I did notice on an earlier posting concerning Publishing, that the toolset option was not available either in the screen dump

http://www.ventanasystems.co.uk/forum/v ... php?t=4053

I've just tried publishing both an old model and a new one I created, both times the include toolset option is available.

Are you publishing your model for use by others in the Vensim Model Reader, or in a VenApp or something like Sable. In the VenApp/Sable method you can always work around the non packaging of the toolset by distributing the toolset with the model, and then automatically loading it from within the Venapp or Sable, using the

SPECIAL>LOADTOOLSET|{toolname} command.

Sorry I can't be of more help at this point.

[ajclarke]

I am using Sable, but the model doesn't get linked in e.g. it is listed in Sable under model, but the pop down lists are all empty as are the graphs e.g. it has my screen designs but doesn't pick up the model data...

[ajclarke]

Also you mention SPECIAL>LOADTOOLSET|{toolname} command.
Do I need that? I am not aware that I am using a toolset but I do have macros in the model.

I only wanted to tick it because that is what Tony's bitmap had ticked...

[Wilson]

AJ,

If you are not using a customized tool set, then you will not need to use the check box.

The model drop down box in Sable>Workspace>Properties is the only one which "has" to have a valid entry. So, as long as your VPM file is listed and selected that should be okay.

With regards to your Sable interface, when you create a new Sable project, it makes a copy of the original *.vpm model and adds this to the <model> sub- directory in the Sable Project directory. It doesn't copy any of the vensim results files (*.vdf) you may have already generated from within Vensim, unless you included them in the VPM. If not, you can copy them manually into the <model> directory, or regenerate them by running your model from within the Sable project.

[Also, if you are populating you model with constants from an external source, such as a *.cin file or an excel spreadsheet, they will also need copying into the <model directory.]

Then, if you have some graphs in your sable screens , you should see some results . If not, make sure the run (.vdf) is loaded by adding a button with the command properties:

MENU>LOAD_RUN|?

That will display the same dialog box for loading runs as you see in Vensim.

[bob@vensim.com]

the analysis is right. The toolset option is grayed if you are using the built in toolset. If you have loaded a different toolset then the option should be available. All Vensim configurations have the built in toolset (though there are some differences in the exact tools contained).