<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcq="http://purl.org/dc/terms/"><records count="1" morepages="false" start="1" end="1"><record rownumber="1"><dc:product_type>Journal Article</dc:product_type><dc:title>Explaining and Fixing DFT Failures for Torsional Barrier</dc:title><dc:creator>Nam, Seungsoo; Cho, Eunbyol; Sim, Eunji; and Burke, Kieron</dc:creator><dc:corporate_author/><dc:editor/><dc:description>Most torsional barriers are predicted with high accuracies (about 1 kJ/mol) by standard semilocal functionals, but a small subset was found to have much larger errors. We created a database of almost 300 carbon–carbon torsional barriers, including 12 poorly behaved barriers, that stem from the Y═C—X group, where Y is O or S and X is a halide. Functionals with enhanced exchange mixing (about 50%) worked well for all barriers. We found that poor actors have delocalization errors caused by hyperconjugation. These problematic calculations are density-sensitive (i.e., DFT predictions change noticeably with the density), and using HF densities (HF-DFT) fixes these issues. For example, conventional B3LYP performs as accurately as exchange-enhanced functionals if the HF density is used. For long-chain conjugated molecules, HF-DFT can be much better than exchange-enhanced functionals. We suggest that HF-PBE0 has the best overall performance.</dc:description><dc:publisher/><dc:date>2021-03-12</dc:date><dc:nsf_par_id>10220443</dc:nsf_par_id><dc:journal_name>The journal of physical chemistry letters</dc:journal_name><dc:journal_volume/><dc:journal_issue>12</dc:journal_issue><dc:page_range_or_elocation/><dc:issn>1948-7185</dc:issn><dc:isbn/><dc:doi>https://doi.org/10.doi.102110.1021/acs.jpclett.1c00426</dc:doi><dcq:identifierAwardId>1856165</dcq:identifierAwardId><dc:subject/><dc:version_number/><dc:location/><dc:rights/><dc:institution/><dc:sponsoring_org>National Science Foundation</dc:sponsoring_org></record></records></rdf:RDF>