On Mon, Nov 26, 2012 at 10:41:33AM -0800, cspiel wrote:
> to Enfuse in a for-loop at shell level, e.g.
> for _N in `seq 24`; do enfuse ...; done in your experiments
... and put the output in a distinct logfile each time.
add:
> logfile.$_N
at the end of the logfile.
Or if you want to see the output in your window as well:
| tee logfile.$_N
Add 2>&1 somewhere (I'd have to experiment a bit to remember where) to
get stderr output to the logfiles as well.
Afterwards you can check the logfiles which went bad.
On the other hand, programs like "enfuse" are deterministic. They
should yield exactly the same output given the same input. This
means that "intermittent" problems are a hint that your hardware
is broken.
Read http://www.bitwizard.nl/sig11/ for more info. (I wrote
that over a decade ago, but it's still valid.)
Roger.
--
** [email protected] ** http://www.BitWizard.nl/ ** +31-15-2600998 **
** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
The plan was simple, like my brother-in-law Phil. But unlike
Phil, this plan just might work.
--
You received this message because you are subscribed to the Google Groups
"Hugin and other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
