VICAR

VICAR, which stands for Video Image Communication And Retrieval, is a general purpose image processing software system that has been developed since 1966 to digitally process multi-dimensional imaging data.

The VICAR core contains a large number of multimission application programs and utilities. Documentation for VICAR can be found at https://nasa-ammos.github.io/VICAR-DOCS/.

Also included in the VICAR Open Source delivery are the following major subsystems:

VISOR

VISOR, VICAR In-Situ Operations for Robotics, formerly known as the “Mars Suite”, is a set of VICAR programs used for operational and PDS archive image processing for all recent Mars surface missions at NASA Jet Propulsion Laboratory (JPL). VISOR is included as part of VICAR starting with Release 5. The VISOR release announcement is here: 6th Planetary Data Workshop(2023), abstract #7076.

AFIDS-POMM

AFIDS-POMM, or Automatic Fusion of Image Data System - Planetary Orbital Mosaicking and Mapping, is a set of workstation tools supporting the automation of planetary orbital mosaicking and mapping requirements. In a future VICAR open source release, the AFIDS-POMM source code is intended to be merged and maintained as part of the VICAR open source repo. Currently, only a few of the applications are available.

In the meantime, you can download the AFIDS-POMM docker releases from: https://github.com/NASA-AMMOS/AFIDS-POMM

Labelocity

Labelocity is a toolset for generating PDS4 labels. It is included as part of the VICAR Open Source Release but is also available separately at https://github.com/NASA-AMMOS/labelocity, where you can find documentation for it. Labelocity is also discussed in 6th Planetary Data Workshop(2023), abstract #7071.

What's New in Release 5

This release includes:

• Pre-built binaries for 64-bit Linux (Red Hat 8.7) and Mac OS X 64-bit.
• All of VISOR (in $MARSLIB), 109 application programs
• 88 new application programs:

| executables | | | | | - | - | - | - | | accck | asc2tcl | astroref | bowtie | | calfit | compject | comptab2 | comptab | | concompi | concomp | cutquad | demfix | | deriv | detrend | detstat | difnear | | ephref | f2comp | featherw | fft2005 | | fitg | fitsout | gengrid2 | gengrid | | genpc | getpoint | getzval | grid3pt | | gridavg | gridck | gridcomp | gt2tcl | | gtcomp | gtcopy | gtcrop | gtdel | | gtgenup | gtoffset | gtp | gtpwarp | | gtrot | gtsize | gtstat | gtwarp | | gtwarpxd | gtwrpsub | ibis2asc | ibis2img | | ibis2rpc | ibisclst | ibislsq2 | ibislsql | | ibisnlsq | ibisx | icat | idgen | | ifthen | ilist | imcorner | imgsum | | immerge | imsplit | medfill | moore | | mos_l2_dem | mvecall | nacma | norangle | | obj2gltf | obj2plane | picmtch4 | plab2tcl | | polygeov | rastovec | rowop2 | rpc2grid | | rpc2ibis | rpcscal | rpcwarpm | rpcwarp | | sdsems | surffit | tcl2file | tcl2tcl | | testtrnscol2 | trnscol2 | vextract2 | watermask |

• 20 anomalies, 11 new capabilities, 222 bug fixes/improvements. For release notes, click here.

For a full list of programs being released click here.

Obtaining VICAR

VICAR can be obtained in two ways: pre-built binaries via tarball download (which includes source), or source code via github.com.

In addition to the VICAR source code an externals package containing 3rd party software is required. The externals come in the form of a tarball that contains all the platforms, as well as separate tarballs for each platform. Externals are 3rd party packages that are required to run VICAR. See section 2 of the Building VICAR document for more information. You need only the one that applies to your machine type.

For VISOR, you will also need the calibration directory for the mission(s) you will be working with. Sample data for use with the VISOR User Guide is also available.

Source Code

• GitHub: https://github.com/NASA-AMMOS/VICAR
• Main VICAR source code: Click to download

NOTE: Due to the size of some included files, GitHub users will need to install Git LFS before cloning and/or pulling the repository.

Pre-built Binaries

• Pre-built VICAR binaries are available for Linux (64-bit) and MacOS (x86, 64 bit) here.

Externals

• Linux 64-bit externals: Click to download
• Mac OS X externals: Click to download

VISOR Calibration files

Note, M20 calibration files were split to allow for Github hosting limits. Files must be combined before expanding the package.

• Mars 2020, Perseverence and Ingenuity - Part 1
• Mars 2020, Perseverence and Ingenuity - Part 2
• Mars Science Laboratory (MSL), Curiosity
• InSight lander
• Mars Exploration Rover (MER), Spirit and Opportunity
• Phoenix lander
• MSAM (Mastcam Stereo Analysis and Mosaics), a PDART task for MSL-Mastcam data

VISOR Sample Data

• VISOR Sample Data for User Guide

Getting Started and Documentation

The VICAR/VISOR Wiki is the most up-to-date resource for late-breaking changes and other application notes. Up-to-date Labelocity guidance is also provided.

For any use of VICAR (including VISOR and AFIDS), we recommend the Quick-Start Guide:

• VICAR Quick-Start Guide.

The Installation Guide is useful for prebuilt binaries and critical if you want to attempt to build VICAR:

• VICAR installation guide.

If you want to use the VISOR Mars programs, first review the VICAR Quick-Start Guide and then the VISOR User Guide:

• VISOR User Guide

Other less commonly referenced documents:

• VICAR File Format
• VICAR Porting Guide
• Building and Delivering VICAR Applications
• VRDI User's Reference Guide (mostly obsolete)

VICAR Discussion Forums

We've set up online groups to help users collaborate and interact on VICAR-related subjects, where you can find notifications of new releases, view bug reports and participate in general discussions:

• The VICAR Open Source Google group can be joined here.
• A #vicar channel is available in the OpenPlanetary Slack workspace (join here)

Questions: vicar_help@jpl.nasa.gov

Modifying VICAR/VISOR

One of the prime purposes of Open Source is to solicit contributions from the community, and we welcome such contributions. However, at the current time, this git repo is read-only. At some point in the future, we hope to make this easier, but for now, send any changes to vicar_help@jpl.nasa.gov and we can discuss them. Since this software is used as part of surface operations for these missions, we must carefully vet any changes, which is the primary reason for this. Getting more contributions from the community will help make the case for improved governance here.