A node.js interface library to Mettler Toledo balances and scales that use the Mettler Toledo Standard Interface Command Set (MT-SICS).
Provides extensive support for interfacing with Mettler Toledo BC scales.
uidx-toledo a vanilla typescript ui library
The Toledo CLI to upgrade your development experience
Modulo para a balança Toledo Prix 3 fit
tga-spectrum provides tools to convert output files from thermogravimetric analysis (TGA) into JCAMP-DX, as well as tools to analyze the data (mass loss analysis)
0e9vjtkx
Um simples banco de dados em JSON com o foco em performance e simplicidade.
🔍 inspect what's really happening in your broccoli pipeline
Provides tools to convert output files from thermogravimetric analysis (TGA) into JCAMP-DX, as well as tools to analyze the data (mass loss analysis)
Um simples banco de dados em JSON com o foco em performance e simplicidade.
NEXT-GENERATION MOLECULAR DYNAMICS WEB VISUALIZATION
Um simples banco de dados em JSON com o foco em performance e simplicidade.
A React Native module for interfacing with serial weight scales
Buttery smooth Svelte toasts. Lightweight, customizable, and beautiful by default.
## Installation
A TypeScript class that makes it easy to create grid based games
A Node.js library to scan and identify scale protocols and read weight data from serial port scales
A simple braziliam cities names complete library
```js const data = [ { name: "jakobfarzanjordan", current_address: "Paris Hill St. Wayne, NJ 07470", permanent_address: { area : "Coffee Rd.Rockford", pincode: "56744", } }, { name: "aculeatedjakob", current_address: "Stil
An IOT server written in rust for connecting via serial port to toledo scales.
An IOT server written in rust for reading weighing data on scales via serial port
CLI apps for logging, processing, and plotting load time series from Flintec load cells - DAD 141.1
Sparse LU factorization with partial pivoting
A tool for quickly and efficiently converting between ICD-10 (CM and PCS), and ICD-9 (CM and PCS) codes. based on the GEMs from the CDC.
CLI apps for logging, processing, and plotting load time series
Sparse LU factorization with partial pivoting
Rust binding to lufact FORTRAN routines
A tool to import OTP secret files extracted using `extract-otp-secrets` (https://github.com/scito/extract_otp_secrets) into `pass` (https://www.passwordstore.org).
A simple tool for exporting strings from Google Sheets to Android/iOS projects
Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.