Technology Mapping

Explicit Technology Mapping

Typically when using Structural descriptions, its normal to use unary operators to explicitly map microfluidic components to a structural primitive. This allows the LFR compiler to know which components need to be explicitly replaced by a microfluidic component and not to pick a component in the Platform Library.

Explicit Technology Mapping requires 3 pieces to work:

1. Unary Operation on structural primitive
2. #MAP directive
3. Platform Library

The rest of this section will discuss how each of these pieces:

Operators

The #MAP directive needs to have a operator

Unary Operators

• '+'
• '-'
• '!'
• '~'
• '&'
• '~&'
• '|'
• '~|'
• '^'
• '~^'
• '^~'

#MAP Directive

#MAP '<technology-string>' '<operator>'

Example:

#MAP  'MIXER' '~'

Platform Libraries

Platform Libraries incorporate all the components that can be mapped to the design tool. Each platform library also captures a set of rules that describe constraints for architecture synthesis.

Default Technologies

You can find the full list of the components and their respective visualizations on 3DuF.org.

DropX (Coming Soon...)

This library consists of a series of continuous-flow droplet based designs that can perform various tasks on droplets. Variants for CNC-Milled/Photolithography are available are:

• DropX-Makerfluidics
• DropX-Lithography

MacroFluidics (Coming Soon...)

This library consists of a series of continuous-flow designs that utilize laser-cutting/micro-milling and Grover Valves as default valve designs.

mLSI (Coming Soon...)

This library consists of component designs intended for high-density multilayered PDMS designs.