*Apologies, meant to start a new thread:*
Awesome, thanks for sharing beanbuff. March seems to be the #ingest month 
:).

I'm curious though: what is the fundamental concern around representing 
thousands of temporary positions in Beancount? Is it performance, and if 
so, won't v3 solve this? Is it to not pollute your ledger with distracting 
short-term transactions, and if so, wouldn't a better approach be to put it 
in appropriate accounts in the hierarchy that don't distract? I'd imagine 
the pros of putting it in Beancount would far outweigh the cons 
(performance not withstanding), given you can focus your analysis tools on 
one system (Beancount) rather than building a parallel system for it.

Also: why "buff"? :)

On Wednesday, March 31, 2021 at 7:48:27 PM UTC-7 bl...@furius.ca 
<https://groups.google.com/> wrote:
Red: Related to investments, I'm in the process of cleaning up and 
building common data structures specifically for trading accounts, in a new 
repo called "beanbuff". Find related codes here:
https://github.com/beancount/beanbuff/tree/master/beanbuff
At the moment it's just the importers I'm sharing, but I'm working on 
making the conversion to an intermediate trade log consistent across them 
and to convert that trade log to Beancount. I'm finding that having a flat 
table trade log is more useful for analysis and am still on the fence about 
representing thousands of 1000's of transactions for temporary positions in 
Beancount inputs. I tend to separate the long term stuff (e.g., a long 
position on an ETF held for years, with associated covered calls) from 
active trading (e.g., a strangle on BIDU held for 20 days, a /ZCN21-/ZCZ21 
calendar spread, etc.), those things don't matter much in the long run and 
I think it might make more sense to summarize the impact of trading to just 
a single transaction per week and to keep all the detail in separate files 
analyzed by custom scripts doing various breakdowns on P/L.

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/b58745fe-ad33-4755-ade6-87e8314e44a3n%40googlegroups.com.

Reply via email to