| Glad to see one of my pet peeves strike a chord. I've always wanted functions to have multiple return values like they have multiple arguments, but all of the solutions I've seen break every calling site when you go from one to two return values. Here is the bit I wrote in the doc: | |
| ## Associated results | |
| The result of a code block is the final value of the subject. However it is often desirable to return extra results from a function call. For example, integral division would like to return not only the integral ratio but the fractional remainder as well. This is done as follows: | |
| ``` | |
| integral-divide ()= 1 do{ | |
| divisor: 1 | |
| numerator = $ | |
| := numerator / divisor floor() |
This repository houses the working data of the IMERSS biodiversity informatics working group together with algorithms for transforming, reconciling and projecting observation and checklist data into formats suitable for publication, submission to global authorities such as GBIF, as well as map-based and graphical visualisations.
All data is stored in CSV files in subdirectories under data although some unprocessed checklist data is a
This package implements a map and query-based visualisation of data on Ontario COVID-19 assessment centre locations for project We Count.
It includes built-in data that merges the ODS assessment centre locations dataset with a mocked accessibility dataset for these assessment centres to visualize at [data/merged/output.csv].
This file documents the full data pipeline necessary to reproduce the data pipeline responsible for exporting catalogue and summary data for Volume I of the Galiano Data Paper, given the raw upstream catalogue data and curated summaries as input.
Firstly, clone and install this repository using instructions listed in README.md, reproduced here:
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog. Infusion from v2.0.0 onwards adheres to Semantic Versioning.
Algorithms for processing and relating data in ways which promote ownership, representation and inclusion, maintaining rather than effacing provenance. See slide 2 in presentation Openly authored data pipelines for a recap of Project WeCount's pluralistic data infrastructure goals.
| Problems with syncretic promotion - we handled post-advice, but not pre-advice. | |
| Consider the following: | |
| elements: { | |
| output: { | |
| type: "fluid.csvFileOutput", | |
| input: "{joined}.data", | |
| filePath: "outputData/output.csv", | |
| writeProvenance: true | |
| // provenance: "provenance.csv", |
Algorithms for processing and relating data in ways which promote ownership, representation and inclusion, maintaining rather than effacing provenance. See slide 1 in presentation Openly authored data pipelines for a recap of Project WeCount's pluralistic data infrastructure goals.
In this article, I'd like to explain why I think The Elm Architecture is fine for small components, but quite harmful for websites based on pages.
First, let's clarify what I mean by "The Elm Architecture".
The Elm Architecture's webpage describes it pretty well.
| 1 i=0 | |
| 5 CLS | |
| 10 SCALE 256,-189.5,-128 | |
| 20 FOR a=0 TO 100 STEP 5E-2 | |
| 30 i=i+1 | |
| 40 x=(((SIN(SQRT(a))*COS(a/20))+1)*255) | |
| 50 y=(((SIN(a/20)+SIN(a^.7)+2))*31.5) | |
| 55 x=INT(x+.5):y=INT(y+.5) | |
| 57 BLOCK 2,1,x,y,i | |
| 60 BLOCK 2,1,511-x,y,i |