These are common instructions for my VMD plugins.
Before you begin. Download the latest release and extract it in a directory of your choice.
import pandas as pd | |
dl = [] | |
d={} | |
with open("J_Medline.txt","r") as f: | |
for l in f: | |
l = l.strip() | |
if "----" in l: | |
dl.append(pd.Series(d)) | |
d={} |
Toni: I see two ways to distribute the software:
Semi-manual install using Vagrant. Draft instructions are below, based on Ismael's. All the relevant repositories must be made publicly-readable.
Alternatively, distribute a self-contained, pre-ready "Vagrant Box". The latter should be easy and stable (doesn't depend on external downloads disappearing) but I have not tried it yet. There shouldn't be software license problems
Neither of the two works right now, because of some missing initialization.
(Current as of Aug 2019)
Clone the official HTMD repository.
git clone https://github.com/Acellera/htmd
#!/usr/bin/env python3 | |
# Replaces xxd -i for systems without it (e.g. conda). Only stdin. | |
import sys | |
import textwrap | |
data=sys.stdin.buffer.read() | |
#xdata=", ".join([hex(x) for x in data]) | |
xdata=", ".join([f'0x{y:02x}' for y in data]) |
/* | |
* Test autodifferentiation of a function computed via an iterative | |
* algorithm (Newton's method). | |
*/ | |
#include <cmath> | |
#include <stan/math/rev/mat.hpp> | |
#include <time.h> |
Using Fedora's ipopt | |
../configure --prefix=$HOME/Apps/jmodelica --with-ipopt=/usr --with-eclipse=$HOME/Apps/eclipse | |
make | |
export SUNDIALS_HOME=/home/toni/compile/JModelica.org/build/sundials_install | |
export JAVA_HOME=/usr/java/latest/ |
Turns out that an Android tablet (actually any phone) can be made into an actually-useful full-fledged Linux workstation, without rooting it.
By actually-useful, I mean something that a power-user will be able to use. By power-user, I mean roughly somebody who does most of his work in the command line and/or editors, but in a graphical environment.
There is no way around the fact that GUI-based tools developed for a desktop system will be unusable on touch interfaces. For one, UI elements are simply too many and too close together.
Command-line tools are quite another story. Lots of scientific and development workflows rely on some form of console or editor, plus an occasional preview - say a plot, or rendered LaTeX output. The key here is the ability to easily switch windows, and that they appear with sensible defaults that don't force us to rearrange them every time.