BoltzTraP error


Hello users,

I am trying to calculate the electronic transport properties using the boltztrap module of the electronic structure package. My attempt is uploaded in this github page

The error I get is the common factorisation error, which occurs due to low k-grid.

Can someone please identify, what I need to do in this code to correct this error?

George Yumnam


It looks like you are trying to run BoltzTraP using line-mode band structures. The band structures returned from MPRester are across high-symmetry lines in k-space only.

For running BoltzTrap, you need the eigenvalues from a dense uniform k-mesh. MP computes these and has the data but has not made this available through the REST interface. There is some votes for this capability inside the “request features” of MP.

The future plan is to open up the uniform k-mesh band structures on the MP platform very soon. We are going to submit a paper on the results of our Boltztrap calculations so far and at the same time allow users to download uniform k-mesh band structures from MP. You could then feed those band structures into Boltztrap.




I was interested in using this transport data, and located it in the Dryad repository. But, I was just wondering whether the data has since been made available through the REST API interface.

Thank you,


Hi Ramya,

Thank you for your interest in our BoltzTraP data. Francesco Ricci, who uploaded the data to the Dryad repository, has also contributed it to MP through our new MPContribs platform:

Log in with your Google account and click on to the Carrier Transport data set.

Documentation to programmatically retrieve contributed data via the MPContribs API is at

Click the “launch binder” badge in the “Tip” section, to start an example Jupyter notebook for the carrier_transport data on BinderHub. This doesn’t require any installation and you can download the notebook as well as the data you need afterwards.

You are one of the very first ones we’re referring to this new infrastructure. So, happy to hear your feedback, and please let me know if you have any questions or run into any issues.