How to Download Jobs scheduled by a specific User on Polyspace Job Monitor from a group of Jobs scheduled by Multiple user ?

Currently we have option to download jobs by giving the JobId , but I would like to Download Jobs scheduled by a specific User on Polyspace Job Monitor where other users have scheduled their job too.

I could find that we use the -author keyword to schedule the jobs , but couldnt find info on the same while downloding the jobs

Using the below command to download jobs based on a Job Id

'"C:\Program Files\Polyspace\R2019b\polyspace\bin\polyspace-jobs-manager.exe" download -job 6406 -results-folder C:\Projects\Polyspace\6406' 

the command below with the author name didn't work

'"C:\Program Files\Polyspace\R2019b\polyspace\bin\polyspace-jobs-manager.exe" download -author amar -results-folder C:\Project\Polyspace\6406'

Post this i would also like to download specific JobIds scheduled by a particular user.

Please help on the same

[Ami]

@Anirban : Addtionally we would like to know if there is an arguments that can be passed along with “listjobs” which will enable us to get details of jobs within a specific range of listed jobs on the Job Monitor or based on the Author name or Date or server address .

For eg. we have 7000 Jobs Listed on the Job Monitor , now we are interested in getting the data only for jobs between the range 5000 to 5500 which are added by a given user , say "AMAN" , between the dates 10th July 2022 to 12th July 2022

Right now “listjobs” dumps all the data from the job monitor on the command window which takes a lot of time (10-20 min.) when we have thousands of jobs listed on the server.

If you can provide us with any command readily available to parse the data from the job monitor based on the AUTHOR name , DATE , etc. that would be really helpful.

Similarly any command with additinal argument to download the result files from the Job Monitor based on AUTHOR name , DATE , etc. is needed

[Anirban]

Right now, there is no user-facing way to list a subset of jobs, but you can clean up old jobs from time to time to avoid the issue. To clean up jobs, you have to do the same thing as download:

• Get the list of jobs using polyspace-jobs-manager listjobs. The list should contain the job ID-s along with date-s.
• Use polyspace-jobs-manager remove to remove job ID-s that span specific dates in the past.

[Ami]

Thanks for the Info @Anirban , The Polyspace Metric Server is used across multiple teams , so we wont be able to able to clean up the jobs , thats the reason this functionality is required at our end , if possible request you to please see if this feature can be implemented in coming version of Polyspace.

[Anirban]

The Polyspace Metrics server is different from the MATLAB Parallel Server (formerly MATLAB Distributed Computing Server) server used for running jobs. Cleaning the jobs from the latter should not affect the results stored on the former. The basic idea behind the MATLAB Parallel Server workflow is that several users offload an analysis to a server, where the analyses run in a queued manner. Once the analysis is complete, the results can be downloaded to the desktop or uploaded to Polyspace Access (formerly, Polyspace Metrics) for review. There is typically no need to keep the jobs list once a job is completed.

Anyway, please contact MathWorks Technical Support. Maybe they can suggest ways to simplify your workflow.

Answer 1

[Anirban]

You can use:

polyspace-jobs-manager listjobs -scheduler schedulerName

To list all jobs. The list should show the author of each job. You can write a small script to get the ID-s for an author, and then download all jobs using those ID-s.

Answer 2

[Ami]

Hello @Anirban , I had already implemented the solution you suggested , before I posted this question , I was feeling that Matlab will provide me a solution that is better and runs faster.

I feel Polyspace should include this feature to not only download the Jobs using Job ID's but also using using the Username / Date / Time Duration etc. Shouldn't be a very big feature to update

[Anirban]

Thank you! A feature request has been created.