<xml>
  <records>
    <record>
       <contributors>
          <authors>
             <author>Al Marzouk, A.A.</author>
             <author>Erdelyi, B.</author>
          </authors>
       </contributors>
       <titles>
          <title>
             An Accurate and Efficient Numerical Integrator for Pair-Wise Interaction
          </title>
       </titles>
		 <publisher>JACoW</publisher>
       <pub-location>Geneva, Switzerland</pub-location>
		 <isbn>978-3-95450-180-9</isbn>
		 <electronic-resource-num>10.18429/JACoW-NAPAC2016-TUPOB14</electronic-resource-num>
		 <language>English</language>
		 <pages>514-517</pages>
       <pages>TUPOB14</pages>
       <keywords>
          <keyword>ion</keyword>
          <keyword>proton</keyword>
          <keyword>software</keyword>
          <keyword>operation</keyword>
          <keyword>simulation</keyword>
       </keywords>
       <work-type>Contribution to a conference proceedings</work-type>
       <dates>
          <year>2017</year>
          <pub-dates>
             <date>2017-01</date>
          </pub-dates>
       </dates>
       <urls>
          <related-urls>
              <url>http://dx.doi.org/10.18429/JACoW-NAPAC2016-TUPOB14</url>
              <url>https://jacow.org/napac2016/papers/tupob14.pdf</url>
          </related-urls>
       </urls>
       <abstract>
          We are developing a new numerical integrator based on Picard iteration method for Coulomb collisions. The aim is to achieve a given prescribed accuracy most efficiently. The integrator is designed to have adaptive time stepping, variable order, and dense output. It also has an automatic selection of the order and the time step. We show that with a good estimation of the radius of convergence of the expansion, we can obtain the optimal time step size. We also show how the optimal order of the integration is chosen to maintain the required accuracy. For efficiency, particles are distributed over time bins and propagated accordingly.
       </abstract>
    </record>
  </records>
</xml>
