blp | Pythonic interface for Bloomberg Open API

Your image is 4-channels of 32-bits each. PIL doesn’t support such images - see Available Modes here.

I would suggest tifffile or OpenCV’s cv2.imread(…, cv2.IMREAD_UNCHANGED)

I figured out with xbbg blp.bdp function which does similar thing. This is a good substitute if you have a massive bbg function pulling RT price. PyXLL allows you to input an array of tickers which saves a lot of time. I hope this could save someone some time :)

This is the KRW FRD screen in the Bloomi Terminal:

If you hover the mouse over the 3M outright Bid (in the circle), the pop-up shows the underlying ticker to be KWN+3M BGN Curncy.

When I put this ticker in Excel as: =BDP("KWN+3M BGN Curncy","BID","UpdateFrequency",500) then I get updating bid side pricing which matches the Terminal screen.

Since the underlying DAPI for Excel and Python is the same, I would guess that this ticker will work with the blpapi too. I usually find it is quicker to test tickers and fields in Excel.

It is best to group similar securities together when pulling in historic data. In the OP's question, 'TPXDDVD Index' is a calculated total return index. Hence it will not have the same fields available as the other two, which as their tickers suggest are quoted funds.

Taking just the two quoted funds, SCTOGAA LN Equity and VAPEJSI ID Equity, we can determine the default currency in which each field is denominated. This being Bloomberg, naming conventions are organic and may not be obvious! The two value fields are FUND_NET_ASSET_VAL and FUND_TOTAL_ASSETS, and the default currency might be different for each.

We can use the bdp() function to pull back these currencies as follows (NB tickers are in a python list:

It seams PIL and crop has some problems with LZW compression. Removing the compression with Photoshop makes the script running like expected.

You are specifying the parameters incorrectly. The function does not understand the CHAIN_POINTS_OVRD value, so is falling back to the default of 1, which is why the returned dataframe only has one value.

With xbbg you can usually supply Python types, with the override name becoming the parameter name (no quotes) in the bds call. So in this case the date override can be a datetime value, and the chain points override can be a number.

The output in Excel of this formula:

=BDH("TSLA US Equity","PX_LAST,IVOL_Delta,VOLUME_TOTAL_CALL",D2,D3,"IVOL_MATURITY","Maturity_90D","IVOL_DELTA_LEVEL","DELTA_LVL_25","IVOL_DELTA_PUT_OR_CALL","IVOL_CALL")

is:

You can get the same data using the xbbg package. There are plenty of wrappers for Bloomberg in Python, but this one is my personal favourite (pip install xbbg)

Xbbg uses an 'exchange' purely as a method for working out the timezone and trading hours for calls to the underlying Bloomberg API (as the API only takes a start and end UTC date/time).

The reason that "CL1" works and "S 1" doesn't is that the former ticker is listed in the default xbbg assets.yml file. This file provides a lookup of common tickers to identify their trading hours / TZ. The 'exchanges' are listed in exch.yml.

The parameter name to use for tickers that are not in assets.yml to specify CME is 'ref':

The order for selective bloom is still the same:

1. Make all non-bloomed objects totally black
2. Render the scene with bloomComposer
3. Restore materials/colors to previous
4. Render the scene with finalComposer

Patch model's material, having a common uniform, that indicates which render will be used: