Select Home in the top right corner when complete and the main screens will be updated with the new group(s) and link(s).
While this technically isn’t an official solution from Hamilton, many find it and its predecessor useful and much of version 2’s functionality has been incorporated into VENUS 6’s new UI.
Apologies for the ping as this is relevant for this post, but is it confirmed that Method Manager 2 works with Nimbus HD?
I downloaded it, but experiencing the same issue where it struck on the loading screen. I’m running Venus 4.6.0.7995 on Window 10 Pro, and I restarted the computer after the download, but no luck. I just wanted to make sure unless there’s a specific version for Nimbus
I did try that suggestion, but no luck still. Considering that I am working on a fresh computer, do you know of any other OS dependencies required for Method Manager?
@EricSindelar_Hamilton Is there a way of interacting with UI features programmatically? For instance, if I want to add multiple methods in the shortcuts menu without adding every method manually, how can i achieve that?
When setting up Method Manager 2 on multiple PCs, we usually suggest setting it up all the method links on one PC, then copying the entire “Method Manager 2” folder over to the other PCs. This will carry over all the links without having to re-add them.
That said, it is possible to add the links programmatically. Inside the folder for Method Manager 2, there is a subfolder called ‘db’. This folder contains several JSON files which are updated when adding a new link to the manager. These can be updated outside of the application, after which the changes will be represented within the app itself:
I don’t have information on all the specifics, but I can say that the icon references can be found in “html\css\all.min.css”, in case you need to use that to adjust the icons programmatically as well.
On the chance you’re referring to the new VENUS 6 GUI, I am not aware of a way to programmatically update those links, but it is possible to export/import the shortcuts between PCs by using the menu in the upper-right corner of the Settings page.
Unsure if anyone has brought this up anywhere on the forum, has anyone had issues running protocols within Method Manager 2 in Lab Operator user group? Our lab set up a new computer with Venus 4 freshly installed for ML STAR, and have an Administrator account set up as well as a Lab Operator account. The Administrator account can run all protocols linked to Method Manager, including daily/weekly maintenance. However, the Lab Operator cannot open any (the mouse cursor will indicate that the protocols are clickable, but nothing happens). Lab Operator still can run directly through Method Editor or Hamilton Run Control so users can still access the protocols. However, all our documentation references running through Method Manager and it’s generally much more user friendly.
Is there a configuration setting (through Method Editor system config spec or through Windows) that needs to be updated in order for the Lab Operator account to be able to use Method Manager? All our other instruments can open protocols in Method Manager as Lab Operator and the user groups have been properly assigned in Windows.
This is less likely related to Method Manager and which VENUS group you are a part of and more likely related to Windows group policies blocking programs from opening another program. Typically, when a user is set to Lab Operator, they are also more restricted in general on that computer as well (not admin).
A good test would be to log in to your admin account, change that account to Lab Operator, log off and log back in and see if you can start a method without issue. If it works, that means there is a Windows policy difference between the Admin and the other account that is blocking Method Manager 2.
Thanks for your response. I tested by changing one of our admin accounts to Lab Operator, and was unable to open any methods through Method Manager using that account after the switch.
I’m not exactly sure why that is the case since we are able to open with “Lab Operator” on our other instrument computers. (this is the same Lab Operator account that was added as user groups during installation of Venus)
Edit: shortly after posting this, our local Apps person asked if the folder was on an account with admin access, which gave me an idea. I selected just the Method Manager 2 folder and modified the permissions for the Lab Operator role, which allowed me to run methods using that account! I tried comparing to other instrument computers but the accounts were not set up in quite the same way (had access to power users instead of listing user groups that were added through Venus installation)
