Christopher Dunn

Always prefer a "release". But for now, `master` is the same as `0.7.1`.

> I've mitigated the heartbeat issue a little by raising the rate from 10s to 10m. The default heartbeat is too short. You're doing it right. However, the interval of...

Yeah, coding is always the easy (and fun) part. But git is worth learning. Put the script into `mains`, with a nice long unique name.... Actually, we should probably put...

Maybe we need an extra option so we can ignore the heartbeats by default. It would not be easy for me to diagnose the problems you're having remotely.

You can set `HEARTBEAT_RATE_S=1000` in `pypeFLOW/pwatcher/fs_based.py`. But I'll release something pretty soon which turns the heartbeat off by default. It seems that we only need it internally, so I'll add...

Try the `1.7.5` release. - https://github.com/PacificBiosciences/FALCON-integrate/releases/tag/1.7.5

Let's see if that helps. If not, then the problem might be in how often we check for finished jobs, indicated by sentinel files. That's easy to adjust, but I...

You can look into a particular job directory and look at `pwatcher.dir/stderr`. (The top-level log is rarely useful.) That might tell us exactly what happened, if the job actually started....

It's very difficult to debug remotely. If you don't see any stdout/stderr in any `pwatcher.dir`, then the jobs are not actually starting. In that case, it's possible that your Grid...

> Your documents give 3 scenarios for types of installation, but none of them actually do the make install. `make all` runs the following in **FALCON-make**: ``` 15 all: checklist...