*Operating System: Windows
*BRugs version: 0.5-0
GUI instructions or script (preferred) to produce bug (Use attachment button to add)
I hope that feature requests are also allowed here.
I have been trying to run the same model using different Updaters. With the GUI interface it is easy to disable Updater factories. With BRugs, it is not.
- The modelDisable() function does not indicate success or failure. The only way to know if you have successfully disabled an Updater is to rerun the model (with the same seed) to see if you get different results.
- The GUI does not help the user to find the correct input strings for the modelDisable() function because the GUI uses descriptive labels rather than object names. To find the right input strings, I had to do the following:
- Inspect the R code of modelDisable to see which BUGS commands it called.
- Look in the file Updater/Mod/Messages.odc to see the way that descriptive labels map to factory names
Examine the procedure SetFactory in Updater/Mod/Methods.odc to find that I needed to strip the prefix "Updater" from the factory name.
The BRugs interface could be improved by adding a function that returns a data frame with three columns and one row for each Updater:
- Factory name (matching input to modelDisable/modelEnable)
- Descriptive string (matching dialogue in GUI)
- Indicator of whether it is enabled/disabled.
I appreciate that this is an advanced topic, and may therefore be low priority. But I thought it was worth documenting here.
- Assigned to: