• Code
• Concepts
•   The GPL
•    Filters
•        Overview
•        Filters
•        Standard Filters
• Hardware
• Mathematics

Filters

The Splinescan v4 system will have a number of default filters that can be added to or modified by general users. In the splinescan project, a filter can be described as any application or script which requires and/or produces a file in one of the formats recognised by the splinescan system. A script that links a series of filters together is called a 'batch filter'. The script that controls the entire scanning process is known as the 'scanning pathway' or 'control script'. A filter may call any other filter or external application when it is activated, but may not be called recursively.

Filter Hierarchy

Splinescan filters are divided into a number of hierarchical 'classes'. No filter can process data that has been output from a higher class, but some filters may access data from multiple subservient layers of the class hierarchy. It is possible to use multiple filters from each hierarchical level simultaneously, although the sequence of filters within each class must be piped correctly. As a minimum, each scan must have at least one input filter and one mesh filter to produce a coherent model. The hierarchical structure of the filter system is:

PRE-FILTER<INPUT<ENHANCEMENT<MESH<SKIN.

GOING TO PYTHON
The splinescan project is being designed from the ground up using PYTHON. I tried experimenting with C but in the end, the programming started to overtake the project, and was becoming inaccessible. Python is an interpreted language, runs on most platforms, is easy to learn and is ideally suited to the scanner project.