A form renderer built for React. Create scalable, complex forms at less effort with the power of JSON Schema.
Ｄｏｗｎｌｏａｄ ｅｂｏｏｋ ｐｄｆ ｍｏｂｉ ｅｐｕｂ Al Weckert & Catherine Maillard La Communication non-violente pour les Nuls is available now
formulate is a standalone server that listens for web form data submissions.
A linear programming modeller written in Rust. This api helps to write LP model and use solver such as CBC, Gurobi, lp_solve, ...
reformulate is a standalone server that listens for web form data submissions.
Convex-objective path parameterization for robotic trajectory planning.
Higher-level market workflows, adapters, and dataset helpers for Surge dispatch
Formulating unique assignments recursively.
Camera projection models (pinhole, fisheye, omnidirectional) for computer vision and robotics
.lp file format implementation and external solver invocation for Cbc, Gurobi, cplex, and GLPK
Quantum annealing support for the QuantRS2 framework
A memory-safe interior point optimizer in Rust
Filtre de Kalman adaptatif en virgule fixe pour systèmes embarqués `no_std`, zéro dépendance
Lemniscate-AGM Isogeny (LAI) Encryption – quantum‑resistant cryptography
Now you can parse your LaTeX formules with Katex and let the client-side worry only with stylesheets.
Generate PNG images from Latex formules on your ruby projects
Barman creates the base of your project. It is used by michelada.io to get a jump start on a working app
This gem gives you a beautifully simple way to formulate your linear or mixed integer program. The syntax is inspired by OPL Studio, which remains my favorite linear programming software, but the license is quite expensive.
branch-name is a gem that provides a command-line interface that allows you to accomplish several tasks, tasks I personally find myself having to carry out every time I work on a feature branch. I created this gem for myself; however, you are free to use it yourself, if any of these tasks fits into your personal routine: 1. Formulate a git feature branch name, given a jira ticket and jira ticket description. Why? Because I am constantly having to create git feature branch names that are based on jira ticket and jira ticket descriptions. 2. Optionally create a "project" based on the branch name (formulated in step 1 above). Why? Because I'm constantly having to create folders to manage files associated with the feature branches I am working on. 3. Optionally use and manage default options that determine the git feature branch name formulated, project greated, and default files associated with the project.Why? Because I routinely have to create files to support the feature I am working on and associate them with the feature I am working on. For example: scratch.rb to hold scratch code, snippets.rb to hold code to execute to perform redundant tasks, and readme.txt files to document things I need to remember.