Hi Daniel,
On Apr 18, 5:21 am, D M German <[email protected]> wrote:
> I tried running the scripts, but I got this error (after setting the
> PATH to the current directory). How do I make it work?
>
> d...@phosphorus:/tmp/rip4$ sh makeReference.sh
> makeReference.sh: 16: [[: not found
> makeReference.sh: 16: [[: not found
> makeReference.sh: 16: [[: not found
> makeReference.sh: 16: [[: not found
> ...
There are several possible solutions:
1. use: bash makeReference.sh
I used regular expressions from bash (available from version 3.0) and
they aren't compatible with sh shell (`/bin/bash --version` to check
your bash version).
2. Other possible solution: chmod u+x *.sh and then just run scripts
(ex. ./makeReference.sh).
3. If you want to use sh instead of bash you must modify scripts to
use grep command. Example of new scripts:
makeReference.sh:
#!/bin/bash
testDirectory=`ls tests/`
for directory in $testDirectory; do
tests=`ls tests/$directory`
for test1 in $tests; do
for test2 in $test1; do
$test2=`$test2|grep *.test`
python panoAutomateTest.py -c -p /usr/local/bin/nona tests/
$directory/$test2
done
done
done
makeTests.sh:
#!/bin/bash
testDirectory=`ls tests/`
for directory in $testDirectory; do
tests=`ls tests/$directory`
for test1 in $tests; do
for test2 in $test1; do
$test2=`$test2|grep *.test`
python panoAutomateTest.py -p /usr/local/bin/nona tests/$directory/
$test2
done
done
done
Existing bash script solution is only temporary and running such tests
will be possible with new testing framework.
> With respect to your proposal, I'd prefer that the project is divided
> into two parts. In the first is the creation of basic test cases for the
> tools: mapping of images into different input and output projections with
> different basic parameters. Tests for the optimizer too. Basically, a
> simple set of tests that we can easily run to test regression.
>
> Then you can work on an automatic framework/method to do this
>
> The second part is to do testing a the function level.
>
> I think there are various advantages to this approach. The first is that
> you will get experience on the tools and how the scripts work (and the
> tool parameters). The second is that this test cases are valuable as
> soon as they are created (compared to a framework that needs to be
> finished to be useful).
Yes, I think it is better approach than mine. In my opinion my
proposal is already divided into two (or even 3) parts. Maybe those
parts aren't visible enough. New timeline might look like this:
Part 0 - preparations
May 1st – May 15th - preparations, discussions on mailing list,
research, making developer blog (I am willing to write every two days
reports)
May 16th – May 24th - architecture of the system
Part 1 - tests and framework for the tools
May 25th – June 18th - create full set of tests (including the
PToptimizer)
June 19th – July 4th - creation testing framework for the command line
applications in libpano and integrate existing tests with framework,
add new tests if necessary
July 5th – July 7th - write documentation to the framework
Part 2 - function level testing
July 8th – July 13th - add a special functionality to the libpano, for
checking popularity of used functions – a path for the people who want
to help in development
July 14th – August 2nd - make framework for testing the main
functionality of libpano as used by hugin (function level) and add
tests for the framework (based on popularity checking path)
August 3rd – August 9th - improving of the code, adding documentation,
integrating two frameworks into one, ensuring that frameworks and
tests will work on different platforms, testing
August 10th – August 16th - as above + backup time
Best regards,
Tom
--
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
