Ah, I'll clarify that one further. ``is_valid`` is used for a check on
state (e.g., ``is_valid=has_qual``, in the case of split libraries). Agree
the name should be better


On Mon, Feb 10, 2014 at 8:22 AM, Jai Ram Rideout
<notifications@github.com>wrote:

> In bipy/core/workflow.py:
>
> > +    @no_requirements
> > +    def wf_mul(self, item):
> > +        self.final_state *= item
> > +
> > +    @priority(10)
> > +    @requires(option='add_value')
> > +    def wf_add(self, item):
> > +        self.final_state += item
> > +
> > +    @requires(option='sub_value', values=[1,5,10])
> > +    def wf_sub(self, item):
> > +        self.final_state -= item
> > +        self.final_state -= self.options['sub_value']
> > +
> > +    @priority(1000)
> > +    @requires(is_valid=False)
>
> is_valid is kind of a confusing name in this context, because it sounds
> like you're @requireing that the item is invalid or something.
>
> Maybe have a separate decorator, e.g., @alwaysexec or @alwaysrun or
> something, that indicates whether a workflow method will always be run,
> regardless of validity?
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/biocore/bipy/pull/84/files#r9587038>
> .
>