# Barriers¶

Often part of your control structure depends on previous computations. For example, you might load all the data, and filter some of them out based on a long computation:

from jug import Task

def keep(datum):
# A long running computation which decides whether datum should be kept
...

keeps = [Task(keep, i) for i in inputs]

# Now I want to throw out data
# This will NOT work:
inputs = [i for i,k in zip(inputs,keeps) if k]
results = [Task(long_computation, i) for i in inputs]


This will not work: the keeps list is a list of Tasks not its results.

The solution is to use a barrier():

from jug import Task, barrier, value

def keep(datum):
# A long running computation which decides whether datum should be kept
...

keeps = [Task(keep, i) for i in inputs]

barrier() # <-------- this will divide the jugfile in two!
inputs = [i for i,k in zip(inputs, value(keeps)) if k]
results = [Task(long_computation, i) for i in inputs]


This effectively divides the jugfile in two or more blocks: up to the barrier call and after the barrier call. When a barrier call is reached, if there are any tasks that have not run, then the jugfile is not loaded any further. This ensures that after the call you can load the results of previous tasks.

barrier() is also useful when there are dependencies that Jug cannot see (e.g., one task which writes a file which later tasks rely on). An alternative solution (not always applicable) is to add these dependencies through unused parameters.

## bvalue¶

New in version 0.10: bvalue() was added in version 0.10. Before this version, you needed to call barrier() & value() separately.

bvalue is a more targeted version of barrier, which combines the effect of value() as well. The above example could also be written as:

from jug import Task, bvalue

Note, however, that if there are additional tasks which are not loaded by the bvalue() call, the processing can continue processing them.