Adding in a new instrument - how to initialise MongoDB for the instrument.

[rorymac]

In earlier times to add a new instrument one initialised the instrument in MongoDB with this script: ~/pysystemtrade/sysinit/futures/instruments_csv_mongo.py

This no longer exists

How does won initialise the instrument into Mongo DB?

Also in passing is there a recipe for converting to parquet?

[tgibson11]

This has nothing to do with parquet.

Since long before the parquet changes (the early times?), instrument data has been read directly from the csv config file.

There is nothing to do other than add the instrument to the csv config, if it isn't already there.

[rorymac]

Todd
Thank you, I missed an iteration.

[rorymac]

Just for clarity -
I upload the contract data to mongo, as well as the multiple and adjusted data.
Then check in confing.csv to see if it is there, and for completeness the rollconfig.csv
and simply let the system take its course?

Thanks in advance.

[rorymac]

So followed the "recipe" above and I had a crash in the reports This snippet from the error message leads to believe that the new contract COPPER-mini is incorrectly or not registered somewhere. - In the DB

File "/home/rorym/pysystemtrade/sysproduction/data/contracts.py", line 200, in get_contract_from_db_given_code_and_id contract_object = self.db_contract_data.get_contract_object( File "/home/rorym/pysystemtrade/sysdata/futures/contracts.py", line 41, in get_contract_object raise ContractNotFound( syscore.exceptions.ContractNotFound: Contract COPPER-mini/20230300 not found

I am using version [bcfd966] -- but that is not that old.

What have I missed ?

[meldinman]

Working on this issue now as well. Previously adding instruments was done by splicing csv provided data with updated data to arctic. Data is no longer stored in Arctic so some of these functions need to be updated.
From my understanding if you try to update sampled contracts and the contract currently held in multiple prices is no longer in IB's historical database you will get this error.

[craigmediaservices]

Thanks @meldinman, I was getting stuck on that same error for a few days. Saw the contract values were empty in the database.

Fortunately Rob just auto-updated all the CSVs in develop on Monday and I was able to pull those and successfully update IB to build multiples and adjusted.

I was trying to use the Barchart only method, but there were a bunch of contracts I couldn't locate and it is very slow to collect when starting with nothing.

[bug-or-feature]

https://github.com/robcarver17/pysystemtrade/blob/develop/docs/recent_changes.md

[rorymac]

Thanks