"JP Morgan Employee : But, uh... you guys are under the capital requirements for an ISDA.
Charlie Geller : By how much?
JP Morgan Employee : [thinking] Uh... how much? One billion, four hundred seventy million. So... a lot.
Charlie Geller : This makes us look bad, doesn't it? That we didn't know what the capital requirements were?
JP Morgan Employee : Uh... it's not great. But keep up those returns and give us a call way down the line, you know. Okay?"
Also a security guard kicking out two men in suits from a lobby is just weirdly unrealistic.
I think the issue is that they're bespoke transactions so the credit support required may change depending on the context.
"That's a nice shirt, do they make it for men?"
"Somehow you're like Dora the Explorer and you're the first person who has found this thing..."
"There’s some shady stuff going down. God, this is intimate. I feel like I’m financially inside of you or something."
"I'm jacked. Jacked to tits!"
"Holy shit, that’s just fucking crazy. That’s fraud!"
I find myself quoting this a hell of a lot in the last few years.
https://stackoverflow.com/questions/3730019/why-not-use-doub...
When you're storing balances or transacting payments between institutions, you need to emulate a specific set of operations, part of which includes using fixed point numbers. It is not sufficient to just use fixed point, you also need the correct number of digits (AFAIK it's 4 digits with US currency) you need the correct rounding mode, etc.
Every few years someone comes along with a big new idea to rewrite the aging dinosaur COBOL code that runs the financial world in something modern. It never works. Nobody wants to go through the old COBOL code to figure out exactly what the code does, they take a greenfield approach with a description of what the UI is and an incomplete spec of the operations that need to happen. And then when it comes time to test the system, they get balances and numbers that are wrong. Because the only thing they know is "we need to use fixed point" but never bother to understand the actual full scope of how basic financial arithmetic is unique, and different from "normal" arithmetic.
With numbers that are large enough, a 1% or 0.1% difference means a lot of money. And if you have an automated system making decisions based on those numbers that can translate into financial ruin, legal problems, etc.
Leave the ad hominem aside, btw, noone wants to hear about it.
Apart from in accounting, the two problems with floats are nonassociativity and speed, neither of which are particularly relevant here.
The risk of losing money does not look like subtle floating point rounding errors. It looks like someone fucking up a formula in excel or the model being wrong or the model being right but risk not being hedged.plenty of people in finance will add percentages as x + y instead of doing (1-(1+x)*(1+y)) because it’s simpler (this works fine because log(1+x) is approximately x when it’s small, and it can obviously be made better by taking the log earlier but plenty of percentage inputs to a model may be rough guesses anyway (who cares if you write 5% or log(5%)))
The only way to improve on this description would be to note that the contract rate for each of the persons involved in this endeavor would be in the $485/hour range (of which, the labor provider might get $50). And then to note the 12 layers of management sign-off/approval on top of that - billed separately.
Of course as you say for accounting you don't want to use floating point, but I can't see anything like that in this application.
Why? I assume you're doing this as an advertisment?
But i was working through sigaloid's post here
https://github.com/DidierRLopes/GamestonkTerminal/issues/2
And was still hitting a error on compile
Generally ending with
NFO:pystan:COMPILING THE C++ CODE FOR MODEL anon_model_dfdaf2b8ece8a02eb11f050ec701c0ec NOW. error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
Ran the following to clear the error
sudo apt-get install build-essential libssl-dev libffi-dev python3-dev
Pretty sure libssl-dev and python3-dev were the only ones needed though
Also UserWarning: Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning warnings.warn('Using slow pure-python SequenceMatcher. Install python-Levenshtein to remove this warning')
So the following was needed as sigaloid stated
pip3 install python-Levenshtein
I found Alpaca[1] which looks decent in terms of a stock API and their upstream data provider Polygon.io[2] which looks even better but costs $199/mo for essentially per tick market data.
Either way, as a counterweight to all the conspiracy theory nonsense on the web, I have been making an effort to not assume I know people’s hidden intentions. I’d like to invite you to join me in that.
I don't mind those comments so much, as they can lead to good stuff, but I do mind them derailing the main thread when they are upvoted. So, I often downvote them in retaliation.
Disclaimer, I built findbssales.io
They were using Polygon for data, but if I recall correctly, I believe seeing an email or such that they're going to roll out their own data and discontinue the Polygon "bridge".
In summary, the Terminal (https://github.com/DidierRLopes/GamestonkTerminal) has 7 distinct menus: - Discover Stocks Top gainers; Sectors performance; upcoming earnings releases; top high shorted interest stocks; top stocks with low float; top orders on fidelity; and some SPAC websites with news/calendars.
- Market Sentiment Scrolling through Reddit main posts, and most tickers mentions; Extracting stocktwit sentiment based on bull/bear flags; Twitter in-depth sentiment prediction using AI; Google mentions over time.
- Research Web pages List of good pages to do research on a stock, e.g. macroaxis, zacks, macrotrends, ..
- Fundamental Analysis Read financials from a company from Market Watch, Yahoo Finance, Alpha Vantage, and Financial Modeling Prep API.
- Technical Analysis The usual technical indicators: sma, rsi, macd, adx, bbands, and more.
- Due Diligence Some features are: Latest news of the company; Analyst prices and ratings; Price target from several analysts plot over time vs stock price; Insider activity, and these timestamps marked on the stock price historical data; Latest SEC fillings; Short interest over time; A check for financial warnings based on Sean Seah book.
- Prediction Techniques The one I had more fun with. It tries to predict the stock price, from simple models like sma and arima to complex neural network models, like LSTM. The additional capability here is that all of these are easy to configure. Either through command line arguments, or even in form of a configuration file to define your NN.