-
Notifications
You must be signed in to change notification settings - Fork 3
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:
- Unary Operation on structural primitive
-
#MAP
directive - Platform Library
The rest of this section will discuss how each of these pieces:
The #MAP
directive needs to have a operator
- '+'
- '-'
- '!'
- '~'
- '&'
- '~&'
- '|'
- '~|'
- '^'
- '~^'
- '^~'
#MAP '<technology-string>' '<operator>'
Example:
#MAP 'MIXER' '~'
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.
You can find the full list of the components and their respective visualizations on 3DuF.org.
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
This library consists of a series of continuous-flow designs that utilize laser-cutting/micro-milling and Grover Valves as default valve designs.
This library consists of component designs intended for high-density multilayered PDMS designs.
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.
To be added soon