Menu

#2065 batchmaster "run batch" doesn't allow for one param affecting another

nextrelease
open
nobody
None
5
2019-06-14
2018-11-29
No

I had a case where one parameter's default value depends on another's setting, and this doesn't work properly with the "run batch" tool. For example:

p1= getParam('p1',1,'parameter1',[1,2])
p2= getParam('p2',p1,'parameter1',[1,2])

print 'p1=%d p2=%d' % ( p1, p2 )

when run with the batchmaster will have p2 a constant, even if the scientist didn't specify it. Here I set p1 equal to 1 then 2, but I get the output:

p1=1 p2=1
p1=2 p2=1

when I probably wanted p2 to be p1's value by default.

Discussion

  • Jeremy Faden

    Jeremy Faden - 2019-06-14

    Also it wasn't picking up recently entered jy URIs. This was because it was looking for *.jy in the recent URIs list, so params after the .jy?... weren't matched. Now you can search recent URIs with a Pattern, and this is fixed.

     
  • Jeremy Faden

    Jeremy Faden - 2019-06-14
    1. see https://github.com/autoplot/dev/bugs/2065/interdependentParams.jy
    2. run batch tool, p1 is the first parameter. Let it be 1 then 2.
    3. hit Go!
    4. stdout has p2 always set to 1, even though you'd think it was always equal to p1.
     
  • Jeremy Faden

    Jeremy Faden - 2019-06-14

    This is subtle, and I'm not sure how it should work now. What it's doing is to set all the parameters based on the address bar configuration, and then modify them based on the lists. This is probably acceptable logic, if better documented.

     
MongoDB Logo MongoDB
Gen AI apps are built with MongoDB Atlas
Atlas offers built-in vector search and global availability across 125+ regions. Start building AI apps faster, all in one place.