Leonardo Bernardini

Hi Ondrej,

If you want to submit a job using the REST APIs do not look at the Maya connector because it uses the Muster command line tool (mrtool) to submit the job so it is of no use for you. Consider that you can use it also to submit a job, but let’s assume you want to use the REST APIs that will be also the default method in the future..

Basically you need two steps:

1) Perform a login using a login/password and get back an access token. This requires you to call /api/login and parse the JSON response
2) Submit a job using the queue method and passing also the access token.
3) Optional, deallocate your session by performing a logout

The login URL will be something like this:

http://musterserver:9890/api/login?username=admin&password=mypassword

and you’ll get back a JSON like this:

{
    "ResponseData":
    {
        "authToken": "426200942D0501285315C82F"
    },
    "ResponseStatus":
    {
        "Code": 200,
        "Time": 1339840278,
        "Description": "OK"
    }
}

Always check that the response status is 200 as an additional error check , or the description if it different from 200.

After you get an access token, you can submit the job using a POST REQUEST, the job data must be into the POST data:

http://musterserver:9890/api/queue/actions?authToken=426200942D0501285315C82F&name=submit
{
	"RequestData":
	{
		"job" : 
		{
			"jobName": "my brand new job!",
                	"templateId": 2,
             		"parentId": -1,
                	"dependIds": [],
                	"dependMode": 0,
			"packetType" : 1,
               		"priority": 1,
                	"group": "",
                	"department": "",
                	"packetSize": 5,
			"maximumInstances": 0,
               		"assignedInstances": 0,
                	"attributes":
                	{
                    		
			}
		}
	}
}

Those are the required steps, also you need to pass specific attributes depending on the render engine you’re targeting and you need also to pass information about the post job action you want to run.

Now, the easiest way to construct your basic job template is looking at our integrated web server. If you open it , and submit a job from within the interface keeping the developer tools open in Chrome, you can check how the web application sends the job to muster, and collect the entire POST DATA structure, based on your settings. You can them replicate it from your script.

If you tell me the Maya render engine you’re targeting as well as listing all your job submission parameters, I’ll run it into the web browser for you and give you back the exact POST data to use.

Hope this helps you !

Hi Denis,

Starting with Muster 9.0.13 (that we are going to release today or tomorrow), Houdini PDG networks are supported through a dedicated Houdini PDG script.

Regards.

Ok now it is clear.. the bug you are reporting has been fixed and its due to mrtool muster command Line tool converting the frames submitted with the old flags -sf and -ef to scientific format . Those flags are still used by the maya connector. The bug has been fixed in 9.0.9 so I assume you are on an older version..

sorry I read it wrong, those are just the maya settings, by the way the frame range set into maya has no effect because it’s override by Muster. Could you snapshot the submission panel for the job so we can see the entire settings of the job ?

Hi Eric

No there isn’t any hard limit , frames are mapped to float values and can reach extreme high values . Could you give us further information like the render engine , the start frame , the end frame , the by frame , if submitting from console or web , and the error is getting back

From where you’re logging out the users ? From a python template?

With the current API this sounds a little complex, but we can implement functions like onCustomMessage (that’s actually available from a node to Dispatcher) into the Dispatcher API too, to be able to send messages to connected Consoles as well as Renderclient. By implementing the ability to send messages from/back console to the Dispatcher, you can catch back a response from a modal dialog created with Pyside/QT. We have logged the improvement for 9.0.13 , so you need to wait some days until we release it and your life will be simpler in implementing your request.

Thanks and regards!

When a render fails, it may exit with a code different than 0. This may be due to multiple reasons. The best thing to in such situation is to check the log produced by the chunk you just rendered. Alternatively, and more easy, right click on your node, and select Realtime Log->Enable and open. After opening the realtime log window for that machine, re-init and restart the render. The full log from Maya (are you talking about Maya-redshift right?) with be dumped in that window. feel free to copy and paste in response to this topic. Also I’m moving this topic to Muster 9 because you created it in Muster 5 forum.