From: John Kitchin <jkitchin@andrew.cmu.edu>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: state of the art in org-mode tables e.g. join, etc
Date: Sat, 20 Feb 2021 16:15:02 -0500 [thread overview]
Message-ID: <CAJ51ETrHwwgrzGDxp3gPN39_Njci+rmK4gxSvD15+ym=jhzoYA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2221 bytes --]
Is there a state of the art in using org-tables as little databases with
joins and stuff?
This package https://github.com/tbanel/orgtbljoin
seems close, but not quite what I had in mind. I don't want to modify
tables in place, or create dynamic tables. I do want to combine tables in
memory though for subsequent calculations.
I was thinking more like given the tables from that page:
#+name: quantities
| type-1 | quty |
|----------+------|
| onion | 70 |
| tomatoe | 120 |
| eggplant | 300 |
| tofu | 100 |
#+name: nutrition
| type-2 | Fiber | Sugar | Protein | Carb |
|----------+-------+-------+---------+------|
| eggplant | 2.5 | 3.2 | 0.8 | 8.6 |
| tomatoe | 0.6 | 2.1 | 0.8 | 3.4 |
| onion | 1.3 | 4.4 | 1.3 | 9.0 |
| egg | 0 | 18.3 | 31.9 | 18.3 |
| rice | 0.2 | 0 | 1.5 | 16.0 |
| bread | 0.7 | 0.7 | 3.3 | 16.0 |
| orange | 3.1 | 11.9 | 1.3 | 17.6 |
| banana | 2.1 | 9.9 | 0.9 | 18.5 |
| tofu | 0.7 | 0.5 | 6.6 | 1.4 |
| nut | 2.6 | 1.3 | 4.9 | 7.2 |
| corn | 4.7 | 1.8 | 2.8 | 21.3 |
you would be able to do something like this:
#+BEGIN_SRC emacs-lisp
(join "quantities" "type-1" "nutrition" "type-2")
#+END_SRC
#+RESULTS:
| type-1 | quty | Fiber | Sugar | Protein | Carb |
|----------+------+-------+-------+---------+------|
| onion | 70 | 1.3 | 4.4 | 1.3 | 9.0 |
| tomatoe | 120 | 0.6 | 2.1 | 0.8 | 3.4 |
| eggplant | 300 | 2.5 | 3.2 | 0.8 | 8.6 |
| tofu | 100 | 0.7 | 0.5 | 6.6 | 1.4 |
or, to sum the Fiber column:
#+BEGIN_SRC emacs-lisp :var data=(join "quantities" "type-1" "nutrition"
"type-2")
(cl-loop for row in data sum (nth 2 row)))
#+END_SRC
#+RESULTS:
: 5.1000000000000005
I have spent a lot of time with Pandas in Python lately, and trying to
think through what some analogues with org-tables would be. I would be very
happy not to reinvent the wheel here!
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
[-- Attachment #2: Type: text/html, Size: 3117 bytes --]
next reply other threads:[~2021-02-20 21:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-20 21:15 John Kitchin [this message]
2021-02-21 4:40 ` state of the art in org-mode tables e.g. join, etc Greg Minshall
2021-02-21 6:45 ` Tim Cross
2021-02-21 15:03 ` John Kitchin
2021-02-21 16:23 ` John Kitchin
2021-02-22 6:52 ` Cook, Malcolm
2021-02-22 8:12 ` Greg Minshall
2021-02-22 15:21 ` Cook, Malcolm
2021-02-22 18:41 ` Greg Minshall
2021-02-25 14:50 ` John Kitchin
2021-02-22 8:27 ` Derek Feichtinger
2021-02-24 22:21 ` John Kitchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ51ETrHwwgrzGDxp3gPN39_Njci+rmK4gxSvD15+ym=jhzoYA@mail.gmail.com' \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).