Author Topic: Thinkbox Deadline submission script customisation help?  (Read 3294 times)

2018-03-09, 18:35:54

peterguthrie

  • Active Users
  • **
  • Posts: 250
    • View Profile
    • Peter Guthrie Visualisation
Wondering if anyone has any experience with deadline and corona?

What I'd like to do is have the submission script report the target noise threshold in one of the 'extra info' columns in deadline monitor, and also have the monitor display the current noise threshold as well.

As far as I can work out, corona have done everything they need to do to make this possible, I just dont know how to set it up

thanks!

2018-03-12, 22:34:18
Reply #1

peterguthrie

  • Active Users
  • **
  • Posts: 250
    • View Profile
    • Peter Guthrie Visualisation
have started a thread on the deadline forum, will update here is i get anywhere

2018-03-13, 11:47:07
Reply #2

maru

  • Corona Team
  • Active Users
  • ****
  • Posts: 12764
  • Marcin
    • View Profile
Sorry for the delay. If there is no answer on their forum, or if it takes too long, let us know, and we will contact Deadline about this.
Can you link the Deadline forum thread here as well?
Marcin Miodek | chaos-corona.com
3D Support Team Lead - Corona | contact us

2018-03-13, 12:35:30
Reply #3

peterguthrie

  • Active Users
  • **
  • Posts: 250
    • View Profile
    • Peter Guthrie Visualisation

2018-03-15, 17:07:17
Reply #4

peterguthrie

  • Active Users
  • **
  • Posts: 250
    • View Profile
    • Peter Guthrie Visualisation
Hi Maru,

Would you be able to help Edwin from Thinkbox out? https://forums.thinkboxsoftware.com/viewtopic.php?p=73840&sid=04bf0e015ec40f6e3f481d8852c872f8#p73840

"I think the ideal would be to have the Corona guys provide a MaxScript example of printing that data to the MaxScript listener. I think I could take it from there."

I'm already out of my depth...

2018-03-15, 22:58:02
Reply #5

Frood

  • Active Users
  • **
  • Posts: 1922
    • View Profile
    • Rakete GmbH
Exact for this monitoring reason I made ourselves a custom log loop which provides those information. I don't use deadline but monitor max log files. This is what I get in max.log: one line with all stop conditions and progress:

Code: [Select]
2018/03/15 21:58:55 DBG: [67044] [95212] * Starting custom logger loop.
2018/03/15 21:58:55 INF: [67044] [95212] CORONA : Parsing scene
2018/03/15 21:58:55 INF: [67044] [95212] CORONA : Calculating displacement
2018/03/15 21:58:55 INF: [67044] [95212] CORONA : Preparing geometry
2018/03/15 21:58:55 INF: [67044] [95212] CORONA : Preparing lights
2018/03/15 21:58:55 INF: [67044] [95212] CORONA : Computing sec. GI
2018/03/15 21:58:57 INF: [67044] [95212] CORONA : Pass 1/500
2018/03/15 21:59:00 INF: [67044] [95212] CORONA : Pass 2/500
2018/03/15 21:59:04 INF: [67044] [95212] CORONA : Pass 3/500
2018/03/15 21:59:05 INF: [67044] [98816] CORONA : Passes: 2/500 | Noise: 0.00(1.5) | Time: 00:00:07/01:00:00 | ETA: not yet
.
.
.
2018/03/15 22:00:40 INF: [67044] [98816] CORONA : Passes: 32/500 | Noise: 1.52(1.5) | Time: 00:01:43/01:00:00 | ETA: not yet
2018/03/15 22:00:43 INF: [67044] [95212] CORONA : Pass 34/500
2018/03/15 22:00:45 INF: [67044] [98816] CORONA : Passes: 33/500 | Noise: 1.52(1.5) | Time: 00:01:48/01:00:00 | ETA: not yet
2018/03/15 22:00:46 INF: [67044] [95212] CORONA : Pass 35/500
2018/03/15 22:00:49 INF: [67044] [95212] CORONA : Cleaning up
2018/03/15 22:00:49 DBG: [67044] [95212] * Terminating custom logger loop.


The "CoronaRenderer.CoronaFP" interface and the properties of "renderers.current" provide all information needed -  except ETA as you see. I imagine this could be great to have in deadline :) But Ondra may look into that last missing part before v2 is out. Corona does not keep any secrets usually btw. Just try "showproperties renderers.current" after maximizing your listener :)

I'm no maxscript expert but I could provide the commented log loop if that helps. But from what I've been reading, you just want to access noise level settings and current noise level by maxscript.

For noise stop condition (render setup) this would be:
"renderers.current.target_image_noise_level__error"

For current noise level (updated every 5 passes by default by the renderer):
"CoronaRenderer.CoronaFP.getstatistic(7)"

If you put both into maxscript listener you get your prints. Is it that what you need?



Good Luck



Never underestimate the power of a well placed level one spell.

2018-03-16, 08:22:39
Reply #6

peterguthrie

  • Active Users
  • **
  • Posts: 250
    • View Profile
    • Peter Guthrie Visualisation


2018-03-21, 10:25:30
Reply #8

Frood

  • Active Users
  • **
  • Posts: 1922
    • View Profile
    • Rakete GmbH
To me yes, perfectly. And yes, "Target_image_noise_level__error" is an alias for "adaptivity_targetError". This is the property line you get when you list all Corona properties, sorry if that was confusing. Nothing old/deprecated in here:

Code: [Select]
.adaptivity_targetError (Target_image_noise_level__error) : float
And as I understand, you should be able to see and check your noise target setting in the mentioned "Plugin Info Parameters pane" aren't you?

As for progress: You seem to be more interested in how much time is left, the actual noise level is secondary. ETA calculation is not an easy task when noise level as stop condition is used. A standard progress bar from 0 to 100 is only possible to do with access to the internally calculated ETA imho. This is why I would love to see (maxscript) access to ETA because you cannot do this easily by yourself - or any external application like DL.

But according to Mike O., Coronas ETA should be displayed  in slave Task Render Status like "Rendering pass x (elapsed: y, left: z)".

I cannot check that all because as mentioned I have no DL installation available and never used it, maybe someone having DL could take over. But to me it seems that you already have all information you like to see, even if possibly access to it could be dressed up a bit.


Good Luck


Never underestimate the power of a well placed level one spell.