Re: [HTCondor-users] assigned gpu oddity

[Michael Di Domenico <mdidomenico4@xxxxxxxxx>]

On Mon, Dec 21, 2015 at 4:59 PM, John M Knoeller <johnkn@xxxxxxxxxxx> wrote:
> Yeah. $$ expansion is going to happen against the partitionable slot (the bag of resources) not the dynamic slot that gets created to match the job request.   This is why $$(AssignedGPUs) expands to a list, it's the list of GPUs that the partitionable slot has to hand out.
>
> I think the environment variables that we setup in the slot is the only thing that the job can use to know what GPU it has been assigned.

Ah, that might explain why it used to work and now doesn't.
Originally we had defined a static slot for each gpu detected and then
a last slot as partitionable, we backed away from that into this fully
dynamic mode.

If there's no way to pass the assigned gpus in as a parameter to a
program we'll have to update our documentation, but this does seem a
bit limiting.  we write our own code so pulled the environ isn't a big
deal, but how do people handle binary programs that only take the
assigned gpu device as an argument  are they not using dynamic slots?