CadenceTool/Innovus should set its batch information from Hammer IR

[edwardcwang]

e.g. stuff like this could be generated from the new submit command APIs in Hammer IR instead of hardcoded into projects:

set_db super_thread_batch_command {bsub -q bora -o /dev/null -n 8 -R "span\[hosts=1\]"}
set_distributed_hosts -custom -custom_script_list { {{bsub -q normal -n 8 -R "span[hosts=1]"} 3} {{bsub -q normal -n 8 -R "span[hosts=1]"} 1}}

[colinschmidt]

Its gonna be a bit difficult to do things like the second line here. @jwright6323 you have any thoughts? For reference that command enables you to submit different job commands to different queues or with different settings

[jwright6323]

With the current SubmitCommand APIs you could do this right now but all subtasks would need to use the exact same queues/resources. @colinschmidt how many different configurations do you use in one innovus invocation?

I do also think it's important to separate the concern of "Where does the core instance run" and "How does the core instance farm out its subtasks" while also acknowledging that it's confusing to have a separate LSF configuration in two places. Maybe we can extend the SubmitCommand API to have a subtask field which tools can interpret/use as they wish?