Re: [HTCondor-users] Is there a non-hack way to have a submit description exit and throw an error message?

[John M Knoeller <johnkn@xxxxxxxxxxx>]

The only way I can think of to do that would be to use the "include command" statement in the submit file to run a script that checks all of the input files and sets a variable that the submit file then checks to see if it should abort or not.


Include command : check_inputs.pl
If $(too_many_bad_inputs)
    Error : what's the point...
Endif

Where check_inputs.pl would do it's processing and then have a print statement something like this.

   printf "too_many_bad_inputs = %d\n",  $num_bad > $num_inputs/2;



-----Original Message-----
From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On Behalf Of Dimitri Maziuk
Sent: Wednesday, September 28, 2016 9:44 AM
To: htcondor-users@xxxxxxxxxxx
Subject: Re: [HTCondor-users] Is there a non-hack way to have a submit description exit and throw an error message?

On 2016-09-26 17:21, Michael Pelletier wrote:
> The key thing to remember about the submit description, Dmitri, is
that it's declarative, not procedural. It can take a bit of time to get the hang of that concept, as I know from personal experience, but it's pretty powerful once you do.

My point had nothing to do with programming paradigms, it was that with large batches it is quite common to want "some or nothing". As opposed to all or nothing that's being implemented.

Dimitri


_______________________________________________
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users

The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/