Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to locate configuration file #2

Open
VINIT777 opened this issue Feb 24, 2024 · 10 comments
Open

Not able to locate configuration file #2

VINIT777 opened this issue Feb 24, 2024 · 10 comments

Comments

@VINIT777
Copy link

Can you help me in locating config file where i need to update instrument & sensibull credentials?
Also does it need sensibull premium?

@studiogangster
Copy link
Owner

No need to provide credentials. It will work without it. Just spin the docker-container.
By default, realtime data for all the instruments are pulled.
To customise it, you can update the list of instruments in file:
https://github.com/studiogangster/sensibull-realtime-options-api-ingestor/blob/main/realtime-data/instruments_symbols.js

@VINIT777
Copy link
Author

VINIT777 commented Feb 26, 2024

Thanks for the response - I have few more questions on getting started:
After the docker compose -up - inside the container i did npm start - now this is the output which I got

image

What should i do post this?

Where is the scrapped data folder gets created?

@VINIT777
Copy link
Author

VINIT777 commented Feb 26, 2024

I am trying to get data for say reliance - so i have kept only one instrument in instruments symbol.js as below

image

Do I Need to change anything here as well?

@studiogangster
Copy link
Owner

After spinning up the docker, , look for ".data" directory in the root of project.
It should have the feeds of all the instruments in jsonl format.

".data" is hidden (since it starts with a dot), look for all folders: ls -alh

@VINIT777
Copy link
Author

Thanks for responding - I am able to see data now - but I tried to modify the instrument to get weekly expiry for 22000 strike price for nifty - but it is still pulling data for all the strike prices - also how to know if the pulled data is for monthly or weekly option - please review below :

const instruments =  [
    {
      "instrument_token": 256265,
      "name": "NIFTY 50",
      "tradingsymbol": "NIFTY",
      "underlying_instrument": "NIFTY",
      "expiry": "WEEKLY",
      "strike": 22000,
      "tick_size": 0,
      "lot_size": 0,
      "multiplier": 1,
      "is_underlying": true,
      "is_non_fno": false,
      "tradable": false,
      "broker": "2",
      "mode": "full",
      "exchange": "NSE",
      "segment": "NSE-INDICES",
      "instrument_type": "EQ",
      "last_price": 18877.7,
      "last_updated_at": "2023-10-26T12:47:59+05:30",
      "last_traded_timestamp": 0,
      "sectors": [
        "Index"
      ]
      }
    ];

@VINIT777
Copy link
Author

What modification do i need to do above to get NIFTY 22000 Weekly expiry data?

@studiogangster
Copy link
Owner

For each instrument, aggregated data is collected at once, for every tick.
So, on each line, you will be getting details for all the strike prices.
Further, you can filter out the data as per the requirement.

@VINIT777
Copy link
Author

VINIT777 commented Mar 1, 2024

Yes - Strike price I can filter post data collection as well - but its currently pulling data for monthly options only - how to get weekly option data?

@studiogangster
Copy link
Owner

Currently due to an urgent work, I am unable to update the repo. Will soon integrate weekly expiry in the next release.

@shikharvaish28
Copy link

@studiogangster came across your work - it's beautifully done. Kudos!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants