Planning tool for combinatorial solution mixing. Reach target solutions from mixes of starting solutions, constrained by minimum pipetting volumes. Also aids in computing amounts of powdered reagents required to form solutions with target solutes + molarities.
Project description
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
stock_solutions = [
mx.Solution(
solutes='FA_Pb_I3',
solvents='DMF9_DMSO1',
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
aliasterm 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, calculate_molar_mass, Weigher
powders = [
Powder('Cs_I'),
Powder('Pb_I2'),
Powder('Pb_Br2'),
Powder('Pb_Cl2'),
Powder(
formula='MA_I',
molar_mass=calculate_molar_mass('C_H6_N_I'),
alias='MAI',
),
Powder(
formula='FA_I',
molar_mass = calculate_molar_mass('C_H5_N2_I'),
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.05_FA0.8_MA0.15_Pb_I2.4_Br0.45_Cl0.15',
solvents='DMF9_DMSO1',
molarity=1
)
answer = weigher.get_weights(
target,
volume=1e-3, #in L
)
print(answer) #masses of each powder, in grams
{'Cs_I': 0.012990496098, 'Pb_I2': 0.322706258, 'Pb_Br2': 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.
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file mixsol-1.0.1.tar.gz.
File metadata
- Download URL: mixsol-1.0.1.tar.gz
- Upload date:
- Size: 28.8 kB
- Tags: Source
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.12.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
3a1c660013f2bfaf8250dca144e8d959a7ba667b57877abeb270843d83c609d0
|
|
| MD5 |
fac3bac8745f15c63c80b85eb642e7b2
|
|
| BLAKE2b-256 |
1f77e3a99920ba3c37433f550ab7f028d56b57ff1717c4e3807300ac8ba25348
|
Provenance
The following attestation bundles were made for mixsol-1.0.1.tar.gz:
Publisher:
release.yml on rekumar/mixsol
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
mixsol-1.0.1.tar.gz -
Subject digest:
3a1c660013f2bfaf8250dca144e8d959a7ba667b57877abeb270843d83c609d0 - Sigstore transparency entry: 283641704
- Sigstore integration time:
-
Permalink:
rekumar/mixsol@affac790983140f457963b50e9a5b735bc5cd253 -
Branch / Tag:
refs/heads/main - Owner: https://github.com/rekumar
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@affac790983140f457963b50e9a5b735bc5cd253 -
Trigger Event:
push
-
Statement type:
File details
Details for the file mixsol-1.0.1-py3-none-any.whl.
File metadata
- Download URL: mixsol-1.0.1-py3-none-any.whl
- Upload date:
- Size: 29.9 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? Yes
- Uploaded via: twine/6.1.0 CPython/3.12.9
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
7e24050aff518e2b5fda68985481d354327995a0e6dfafdc42f676402a9f7e79
|
|
| MD5 |
8bfde36d28c729eddc0b7aea760c9f33
|
|
| BLAKE2b-256 |
07c5c7b1105d2d5f982d0f04510b8ce753b95e654306f4612c378afbb9e720e5
|
Provenance
The following attestation bundles were made for mixsol-1.0.1-py3-none-any.whl:
Publisher:
release.yml on rekumar/mixsol
-
Statement:
-
Statement type:
https://in-toto.io/Statement/v1 -
Predicate type:
https://docs.pypi.org/attestations/publish/v1 -
Subject name:
mixsol-1.0.1-py3-none-any.whl -
Subject digest:
7e24050aff518e2b5fda68985481d354327995a0e6dfafdc42f676402a9f7e79 - Sigstore transparency entry: 283641738
- Sigstore integration time:
-
Permalink:
rekumar/mixsol@affac790983140f457963b50e9a5b735bc5cd253 -
Branch / Tag:
refs/heads/main - Owner: https://github.com/rekumar
-
Access:
public
-
Token Issuer:
https://token.actions.githubusercontent.com -
Runner Environment:
github-hosted -
Publication workflow:
release.yml@affac790983140f457963b50e9a5b735bc5cd253 -
Trigger Event:
push
-
Statement type: