For whatever reason, the Edinburgh Festival Fringe got rid of their mobile app this year - a decision that has not gone down too well with punters and performers alike.
CMake manpages are about the most verbose manpages on the planet.
All I wanted to do was import an external project and customise the build options without having to go and add files into the child project / patch them / whatever.
Back in February or so, I’d been covering some ground on atopy and allergies etc and came across a company called IntoleranceLab Ltd (Company #11049115). They claimed to perform “Allergen and allergy testing” with nothing more than a few strands of hair.
Getting copies of annual returns and company information from Companies House is easy. Searching the data in those returns isn’t quite so easy.
CH use a PDF format (PDF/A, akin to fax) that ensures maximum compatability.
I had a small project to display some simple stats for, for some static content sitting in an AWS S3 bucket. I could have forwarded everything to Elastic+Kibana and showed some fancy graphs and charts, but I was only being asked for what I could easily produce via AWStats.
For S3 logging, awstats needs its LogFormat set up in the following manner:
%other %extra1 %time1 %host %logname %other %method %url %methodurl %code %other %extra2 %bytesd %other %extra3 %refererquot %uaquot %other %other %other %other %other %virtualname %other Amazon’s documentation is available here
In my case, I had data stored in a Realm file that I needed to re-export to JSON.
First of all we’ll need Realm Studio. Set up, open the Realm file and then export the models, as shown:
This is more written as an aide-memoire to myself than anything. It’s a process I’m currently using for bulk-processing a set of documents of various forms (MS Word, PPT, PDF, LibreOffice etc), converting them all to PDF, running OCR on any embedded images and then sticking the end-result into Elasticsearch via Tika (not documented, plenty documentation elsewhere re this final step).
See the UI here
Following on from here and here, this is just putting together a couple of blocks from bl.ocks.org to plot data from the PhysioNet site.
Read converting PhysioNet JSON to CSV to import other data sets.
PhysioNet data is available in binary (dat) form but their web site also provides records in JSON.
These records include samples / measurements from 12-lead ECGs recorded at 1ksps.
To convert these to CSV we can use the ol’ jq: