Hi Sophie, Unfortunately no. The problem seems to be that a JDL submission runs the actual commands, whereas an API submission does it all through dirac-jobexec. The dirac-jobexec command only outputs the "Running step 1..." text to the stdout, so the peek only returns that. The real output is stored in a file on the WN and is only accessible at the end in the output sandbox. I don't see any neat workaround for that, but I will double check with the DIRAC developers. Regards, Daniela On Thu, 22 Jul 2021 at 11:16, Sophie King <soph.e.king123@gmail.com> wrote:
******************* This email originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hello
I recently switched to using the API for job submission, rather than writing a JDL and using dirac-wms-job-submit. However, I find that when using the API the 'Peek StandardOutput', just shows some generic info about what I am running, rather than the actual output. Whereas when I used the old method I can I actually peak at my job. If I am testing or debugging, or if something is taking an unusually long time, the ability to 'Peek' was a really nice feature of the GUI. Is there a way to restore this behaviour, while still using the API to submit ?
Cheers Sophie
-- _______________________________________________ Gridpp-Dirac-Users mailing list Gridpp-Dirac-Users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/gridpp-dirac-users
-- Sent from my guinea pig enhanced living room ----------------------------------------------------------- daniela.bauer@imperial.ac.uk HEP Group/Physics Dep Imperial College London, SW7 2BW Tel: Working from home, please use email. http://www.hep.ph.ic.ac.uk/~dbauer/