[Kwiver-users] [MapTk]: [SOLVED] : Configuration File Errors

[R. Pelapur]

Yup. Needs the plugin directory. Works now. Just did an install. Thanks. 
Marking as solved.



On 01/18/2016 03:35 PM, Matthew Leotta wrote:
> The symptom that you are seeing (no valid options listed) usually means that no plugins are being found.  If you are running the tools out of the build directory and not installing them first, you’ll want to enable “MAPTK_USE_BUILD_PLUGIN_DIR” in the CMake options.  This tells the tools to also search the build directory when looking for plugins.  Similarly there is a “VITAL_USE_BUILD_PLUGIN_DIR” in Vital as well.  If all else fails, you can specify the path to your plugins with the VITAL_PLUGIN_PATH environment variable.  There is also a tool in Vital called “plugin_explorer” that will print out info about which plugins around found.  Note, however, that this tool only looks in the build/install directories for Vital.  It will not find plugins in the MAP-Tk build directory unless VITAL_PLUGIN_PATH is set and points to them.
>
> —Matt
>
>
>> On Jan 18, 2016, at 3:27 PM, R. Pelapur <rpelapur at archlinux.info> wrote:
>>
>> Hello,
>> With the new build (commit #59472c9a13db56aee2fd162ae71cabd6e39e6792) now I am getting configuration file errors (config file is the same as the one from what I was running before which did work and is basically the same as the one under /tools/config/)
>>
>>
>> 2016-01-18 14:11:41.322 WARN algorithm.cxx(237): Configuration Failure: invalid option
>> 2016-01-18 14:11:41.322 WARN algorithm.cxx(237): output_homography_generator:type =
>> 2016-01-18 14:11:41.322 WARN algorithm.cxx(237):    valid options are
>> Config Check Fail: output_homography_generator configuration check failed
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): Configuration Failure: invalid option
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): feature_tracker:type = core
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237):    valid options are
>> Config Check Fail: feature_tracker configuration check failed
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): Configuration Failure: invalid option
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): image_reader:type = ocv
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237):    valid options are
>> Config Check Fail: image_reader configuration check failed
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): Configuration Failure: invalid option
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237): convert_image:type = bypass
>> 2016-01-18 14:11:41.324 WARN algorithm.cxx(237):    valid options are
>> Config Check Fail: convert_image configuration check failed
>> ERROR: Configuration not valid.
>>
>> Weird part is that there are no 'valid options'. After using -c -o options to correct the config file iteratively the executable doesn't give any valid options for feature_tacker:type, image_reader:type and convert_image:type.
>>
>> MapTk has been linked against :
>> 1: OpenCV ( 2.4.11) (MapTk use OpenCV)
>> 2: vxl (commit #16dd9bd26af5d530aa2cb4a887b372a157bc4961 - Sat Jan 16 2016) (MapTk use vxl)
>> 3: Vital (commit  #f36957711d08be858e1c05ed170dae3fae75c7da - Tuesday Jan 5 2016)
>> 4: ceres-solver (commit #e9420e7a0e4254337730f574a3242d7e056cbfe8 - Sun Jul 12 2015) (MapTk use CERES)
>>
>>
>> Using GCC 4.9.2 (CentOS 6).
>>
>> Same build configuration and the attached config file but with an older MapTk commit works without problems.
>>
>>
>>
>>
>> <maptk_track_features-sample.conf>_______________________________________________
>> Kwiver-users mailing list
>> Kwiver-users at public.kitware.com
>> http://public.kitware.com/mailman/listinfo/kwiver-users