pip install mixsol

Pipetting planner for efficient combinatorial mixing of solutions. Often we want to interpolate a few stock solutions into many target mixtures. If some of these mixtures require only a tiny amount of a stock solution, the minimum volume for our pipette may limit our ability to make this solution without a serial dilution. Mixsol searches for mixing sequences that use only other target solutions as stepping stones to reach these difficult mixtures, minimizing waste.

Mixsol also has the ability to calculate the masses of solid reagents needed to make a target solution. Finally, measured amounts of solid reagents can be input to calculate the actual solution we have made.

Happy mixing!

Examples

Solution Mixing

Solutions are defined with the Solution class. Solutes and solvents are both defined by either dicts or their formula, which follows the (name1)(amount1)_(name2)(amount2)_..._(name)(amount) format. The names do not have to correspond to elements, so you can use placeholders for units that will be mixed. Parentheses can be used to simplify formulae as well: A2_B2_C == (A_B)2_C. An alias can be provided for the solution to simplify later analysis.

``` import mixsol as mx

stocksolutions = [ mx.Solution( solutes='FAPbI3', solvents='DMF9DMSO1', molarity=1, alias='FAPI' ), mx.Solution( solutes={ "MA": 1, "Pb": 1, "I": 3, }, solvents={ "DMF": 9, "DMSO": 1, }, molarity=1, alias='MAPI' ), ] ```

This process goes for both stock and target solutions.

You can manually generate your target solutions and place them in a list like so:

targets = [] for a in np.linspace(0, 0.8, 5): targets.append(mx.Solution( solutes={ "FA": a, "MA": 1-a, "Pb": 1, "I": 3, }, solvents="DMF9_DMSO1", molarity=1, alias=f'FA_{a:.3f}' ))

Or, if you want to mix in equal steps between two (or more!) endpoint solutions, you can use the interpolate function to generate a mesh of Solution obects. The following code block is nearly equivalent to the one above (it will interpolate all the way from 0-1 instead of 0-0.8, and it won't generate alias values).

target_mesh = mx.interpolate( solutions=stock_solutions, #this should be a list of 2 or more Solution's steps=5 #number of divisions. In this example, steps=5 will mix the input Solution's in 20% increments )

Stock and target solutions go into a Mixer object

sm = Mixer( stock_solutions = stock_solutions, targets = { t:60 #Solution:volume dictionary for t in targets }) which is then solved with constraints sm.solve( min_volume=20, #minimum volume for a single liquid transfer max_inputs = 3 #maximum number of solutions (stock or other target) that can be mixed to form one target )

The results can be displayed in two ways: - plain text output of liquid transfers, in order. use of the alias term really simplifies this output sm.print() ===== Stock Prep ===== 120.00 of FAPI 180.00 of MAPI ====== Mixing ===== Distribute FAPI: 54.00 to FA_0.600 36.00 to FA_0.400 30.00 to FA_0.800 Distribute MAPI: 60.00 to FA_0.000 36.00 to FA_0.600 54.00 to FA_0.400 30.00 to FA_0.200 Distribute FA_0.600: 30.00 to FA_0.800 Distribute FA_0.400: 30.00 to FA_0.200

• a graph of solution transfers. This is harder to use in practice, but can give an overview of the mixing path. fig, ax = plt.subplots(figsize=(6,6)) sm.plot(ax=ax)

Note that the units of volume here are arbitrary. Using SI units for small volumes might cause numerical issues when solving a mixture strategy (eg you should use 10 microliters instead of 1e-5 liters).

Solution Preparation

Mixsol aids in determining the mass of solid reagents needed to form target solutions. We can also check the actual solution formed from recorded reagent masses. Here, the units do matter, and you should stick to SI units (mass in grams, volume in liters).

We define solid reagents with the Powder class. This requires at least a chemical formula delimited by underscores, similar to the Solution definition earlier. If this formula is a proper chemical formula of elements, the molar mass is calculated automatically. If not, you can pass the molar mass directly. The calculate_molar_mass function can be used for convenience. alias does the same thing it did for Solution.

``` from mixsol import Powder, calculatemolarmass, Weigher

powders = [ Powder('CsI'), Powder('PbI2'), Powder('PbBr2'), Powder('PbCl2'), Powder( formula='MAI', molarmass=calculatemolarmass('CH6NI'), alias='MAI', ), Powder( formula='FAI', molarmass = calculatemolarmass('CH5N2I'), alias='FAI', ) ] ```

The list of available Powders is fed into a Weigher object

weigher = Weigher( powders=powders ) which can then be used to determine powder amounts for a given volume of a target Solution

``` target=Solution( solutes='Cs0.05FA0.8MA0.15PbI2.4Br0.45Cl0.15', solvents='DMF9_DMSO1', molarity=1 )

answer = weigher.getweights( target, volume=1e-3, #in L ) print(answer) #masses of each powder, in grams {'CsI': 0.012990496098, 'PbI2': 0.322706258, 'PbBr2': 0.082576575, 'Pb_Cl2': 0.020857935, 'MAI': 0.02384543385, 'FAI': 0.1375746568} ```

Finally, we can also generate a Solution object by inputting a {powder:mass} dictionary into Weigher. We will just use the answer from before, but this can be manually input. result = weigher.weights_to_solution( weights=answer, volume=1e-3, solvents='DMF9_DMSO1', ) print(result) 2.4M Cs0.0208_I_MA0.0625_FA0.333_Br0.188_Cl0.0625_Pb0.417 in DMF9_DMSO1 The molarity of the output will by default be determined by the largest component amount. This can be a bit silly. Passing a component or a numeric value to molarity can be used to manually set the molarity. Note that this does not affect the solution itself, just the relative values of the formula units and the overall molarity.

result2 = weigher.weights_to_solution( weights=answer, volume=1e-3, #in L solvents='DMF9_DMSO1', norm='Pb', #normalize the formula+molarity such that Pb=1 ) print(result2) #result is a Solution object 1.0M Cs0.05_I2.4_Pb_MA0.15_Br0.45_Cl0.15_FA0.8 in DMF9_DMSO1

Solution objects can be compared - even if their molarity/formulae are apparently different, they will show as equal if the effective molarity of each component is within 0.01% between the solutions.

result == result2 True

Read the full documentation here.