From: Ihor Radchenko <yantar92@posteo.net>
To: tbanelwebmin <tbanelwebmin@free.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [ANN] orgtbl-fit
Date: Mon, 20 Feb 2023 10:50:39 +0000 [thread overview]
Message-ID: <87zg98ehkw.fsf@localhost> (raw)
In-Reply-To: <840f139e-d62f-a6ac-8691-b63afb4cd1d6@free.fr>
tbanelwebmin <tbanelwebmin@free.fr> writes:
>>> Examples & documentation can be read here:
>>> https://github.com/tbanel/orgtblfit/blob/main/README.org
>> Interesting.
>> Could it be somehow integrated with TBLFM formulas?
>> I imagine something like
>>
>> ? +?*year +?*passengers +?*(year-2016)*passengers
>>
>> , when set as a column value in table formula, to be auto-updated with
>> actual coefficients upon re-calculating the table.
>> ...
> We need to specify the target column ("consumption" in this example).
> Therefore, the formula could be something like that:
>
> $4 = fit (consumption = ? +?*year +?*passengers +?*(year-2016)*passengers)
> It would benefit from other spreadsheet features, like constants and
> remote references.
Makes sense.
> On the development side, the TBLFM handling is already quite a big chunk
> of code. We must take care that such an additional feature do not add
> complexity and maintenance burden.
From point of view of org-table.el, adding fitting functionality is
mostly delegating the work to GNU Calc. Org side is just parsing the
formula and transforming it to appropriate Calc function call.
So, given that the parsing is extended cleanly, I do not think that
maintenance burden will increase all that much. It may even benefit from
someone taking a fresh look and possibly refactoring org-table TBLFM
parser.
> Orgtbl-fit as-is
> ----------------
>
> It is also possible to include orgtbl-fit as-is into Org Mode core. It
> would sit side-by-side with the core without changing anything in its
> code and its unit-tests.
IMHO, it is not sufficiently integrated with org-table.el facilities in
its current state. I'm afraid that we will have code duplication if
include orgtbl-fit as is.
BTW, the dollar replacement is something org-table can benefit from---a
number of people are confused because "$" is treated specially by Calc.
> Data-analysis toolkit
> ---------------------
>
> From a higher perspective, we could give a consistent data-analysis
> toolkit to Org Mode (and call it org-data-analysis.el).
>
> It would start with fitting, clustering & aggregation. Then, new
> algorithms would be added upon user requests.
>
> Of course, there should be an interest among Org Mode users for such a
> toolkit.
We can, but it should be first and foremost added to GNU Calc. On Org
side, we just need appropriate integration. Maintaining generic data
analysis code in Org is out of Org's scope.
Contributing to GNU Calc will also benefit GNU Calc users who don't use
Org mode.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-20 10:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:40 [BUG] ox-html does not export captions of source blocks without language Johan Bolmsjö
2022-12-14 21:51 ` Kaushal Modi
2022-12-14 22:05 ` Johan Bolmsjö
2022-12-15 9:31 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 10:32 ` Kaushal Modi
2022-12-15 11:32 ` Max Nikulin
2022-12-15 14:29 ` Tim Cross
2022-12-15 15:07 ` Ihor Radchenko
2022-12-17 5:17 ` Tom Gillespie
2022-12-18 1:33 ` Tim Cross
2022-12-17 14:47 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? Max Nikulin
2022-12-18 13:35 ` [BUG] org-latex-src-block-backend is directly used as variable instead of querying export option (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?) Ihor Radchenko
2022-12-18 13:40 ` Timothy
2022-12-21 12:14 ` Ihor Radchenko
2022-12-27 14:18 ` [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does " Ihor Radchenko
2022-12-27 18:39 ` Tim Cross
2022-12-17 9:56 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 13:32 ` Timothy
2022-12-27 14:08 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
2023-01-16 10:09 ` Ihor Radchenko
2023-01-16 10:31 ` [ANN] orgtbl-fit tbanelwebmin
2023-01-24 19:55 ` Ihor Radchenko
2023-01-25 15:02 ` tbanelwebmin
2023-01-26 10:35 ` Ihor Radchenko
2023-01-26 19:13 ` tbanelwebmin
2023-02-20 10:50 ` Ihor Radchenko [this message]
2023-03-01 11:48 ` tbanelwebmin
2023-03-03 15:13 ` Ihor Radchenko
2023-03-05 18:46 ` tbanelwebmin
2023-01-23 13:32 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
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=87zg98ehkw.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=tbanelwebmin@free.fr \
/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).