TypeError while plotting in a for loop about chainconsumer HOT 5 CLOSED

Hi Manodeep,

Ah, whats happening is that ChainConsumer (atm) only allows configure to be called once (and after all chains are loaded in). It is the repeated calls to it that break it, so I would restructure the code such that each chainconsumer instance is only configured once. So if you are just trying to generate plots with different subgroups of parameters, you can configure it once, outside the second for loop, and then call plotter.plot with different lists of parameters.

Also, there is no need to pass in lists of the same option, single options will apply to all chains (ie kde=[False] * nchains is the same as kde=False , which is also the same as not specifying it because kde=False is the default behaviour).

from chainconsumer.

Sorry about the mis-leading with the nchains multiplication, I was trying to solve the assertion error. I hacked my way around the TypeError by checking if the self.config was an empty dict; and if so, creating a list of validated keys. That solved my issue - but I have no idea about the side-effects.

I had the configure right after I called ChainConsumer (before loading the chians). However, then the config options did not seem to take effect; that's why I put the configure within the plotting loop. Just to be clear, if I only call configure after all chains are loaded and before the plotting loop - all should be good?

Thanks again for the quick response.

from chainconsumer.

Ah right, that makes sense. As to resetting config to an empty dict, that should be fine so long as you also set the configured boolean flag to false.

But yeah, from the doco: "Please ensure that you call this method after adding all the relevant data to the chain consumer, as the consume changes configuration values depending on the supplied data."

Some things (like whether or not to shade by default, the opacity of the shaded contours, whether to switch colouring to rainbow, etc) are dependent on the number of chains loaded in, hence the stipulation to call configure (once), after all data has been loaded.

from chainconsumer.

Fantastic - thanks! Sorry I missed that one from the docs.

from chainconsumer.

No worries mate, glad its an easy fix!

from chainconsumer.