#1448 closed defect (fixed)
run model menu item does not seem to work
Reported by: | cmbarton | Owned by: | martinl |
---|---|---|---|
Priority: | critical | Milestone: | 6.4.2 |
Component: | wxGUI | Version: | svn-trunk |
Keywords: | modeler | Cc: | grass-dev@… |
CPU: | Unspecified | Platform: | Unspecified |
Description
I made and saved a model using the graphical modeler. The model works fine. I can load the saved model into the graphical modeler and it works fine.
If I select "run model" from the file menu and select this saved model, nothing happens. No error and nothing produced.
Change History (12)
comment:1 by , 13 years ago
Component: | Default → wxGUI |
---|
comment:2 by , 13 years ago
Cc: | added |
---|---|
Keywords: | modeler added |
Owner: | changed from | to
Status: | new → assigned |
comment:3 by , 13 years ago
follow-up: 5 comment:4 by , 13 years ago
Tested in trunk. Now it runs without an error. But it does not respect the 'parameterization' checkbox when run this way. That is, it does not open a dialog for file selection or module options when the relevant parameterization box is checked. When loaded and run in the modeler GUI window, it does present dialogs for parameterized options. I don't know if this is by design or not.
Michael
comment:5 by , 13 years ago
Replying to cmbarton:
Tested in trunk. Now it runs without an error. But it does not respect the 'parameterization' checkbox when run this way. That is, it does not open a dialog for file selection or module options when the relevant parameterization box is checked. When loaded and run in the modeler GUI window, it does present dialogs for parameterized options. I don't know if this is by design or not.
follow-up: 7 comment:6 by , 13 years ago
Priority: | normal → critical |
---|
follow-up: 9 comment:8 by , 13 years ago
I just tested. Parameterization is now respected in the run model. AFAICT it works fine. Thanks much!
Michael
comment:9 by , 13 years ago
follow-up: 11 comment:10 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Tested and it seems to work fine. I ran into an error initially that I traced to the fact that the output argument for r.blend has changed in GRASS 7 from "output" to "output_prefix" . A more accurate name for the argument but it breaks backward compatibility (permitted across version changes of course).
Thanks again for making this very nice tool for GRASS. I've already been recommending it as a way to get started writing Python scripts. I'll go ahead and close this.
BTW, how does the variables section work for the modeler?
Michael
comment:11 by , 13 years ago
Replying to cmbarton:
BTW, how does the variables section work for the modeler?
http://www.youtube.com/watch?v=RztxMXXtA0s&feature=player_embedded#!
There is an error (check 'command output' if you have no debug level defined).
Hopefully fixed in r48307 (trunk) and r48308 (devbr6). After some testing it could be backported to
relbr64
.