I think it would be fairly useful if scipy contained a module with the entire period table as a Python data type of some sort with various information (atomic number, mass, etc) of all the elements. This sound cool to anybody else?
On 12/17/06, CakeProphet <adamadamadamamiadam@gmail.com> wrote:
I think it would be fairly useful if scipy contained a module with the entire period table as a Python data type of some sort with various information (atomic number, mass, etc) of all the elements.
This sound cool to anybody else?
This sounds pretty cool to me. I think if you were to submit the code someone would be able to include it into the sandbox for testing and review. Cheers, Tim
_______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-dev
How exactly do I submit the source code I currently have written? (sorry, a bit unfamiliar with how this works)
On 12/19/06, Adam Curtis <adamadamadamamiadam@gmail.com> wrote:
How exactly do I submit the source code I currently have written? (sorry, a bit unfamiliar with how this works)
For the time being you can simply send an attachment to the mailing list. I'm sure you'd be able to get svn write access to work on this. I believe Jeff Strunk is the man to speak to to organise this. Cheers, Tim
_______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-dev
Adam Curtis wrote:
How exactly do I submit the source code I currently have written? (sorry, a bit unfamiliar with how this works)
Register for the www.scipy.org wiki and make a page describing your code. Add it to the page as an attachment. When we've seen the code and hashed out the design a little bit, then we'll talk about putting it in the Subversion repository. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
Robert Kern <robert.kern <at> gmail.com> writes:
Adam Curtis wrote:
How exactly do I submit the source code I currently have written? (sorry,
a bit
unfamiliar with how this works)
Register for the www.scipy.org wiki and make a page describing your code. Add it to the page as an attachment. When we've seen the code and hashed out the design a little bit, then we'll talk about putting it in the Subversion repository.
Yeah, you'll probably be doing a lot of review. I'm not exactly known for my legibility.
Robert Kern <robert.kern <at> gmail.com> writes:
Register for the www.scipy.org wiki and make a page describing your code. Add it to the page as an attachment. When we've seen the code and hashed out the design a little bit, then we'll talk about putting it in the Subversion repository.
Alright... the page is up on the wiki. Link: http://projects.scipy.org/scipy/scipy/wiki/PeriodicTable
On 12/22/06, Adam Curtis <adamadamadamamiadam@gmail.com> wrote:
Robert Kern <robert.kern <at> gmail.com> writes:
Register for the www.scipy.org wiki and make a page describing your code. Add it to the page as an attachment. When we've seen the code and hashed out the design a little bit, then we'll talk about putting it in the Subversion repository.
Alright... the page is up on the wiki.
Link: http://projects.scipy.org/scipy/scipy/wiki/PeriodicTable
Thanks for putting that up Adam. It all looks pretty good so far, but the following caught my eye: * All temperatures should be in Celsius. Conversions will be performed by methods (or a package in scipy, if scipy has a unit conversion system) Would it not be better to work in units of Kelvin? In my experience Kelvin is used more often than Celcius in scientific work. What do others think? Cheers, Tim
_______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-dev
On Thursday 21 December 2006 6:05 pm, Tim Leslie wrote:
On 12/22/06, Adam Curtis <adamadamadamamiadam@gmail.com> wrote:
Robert Kern <robert.kern <at> gmail.com> writes:
Register for the www.scipy.org wiki and make a page describing your code. Add it to the page as an attachment. When we've seen the code and hashed out the design a little bit, then we'll talk about putting it in the Subversion repository.
Alright... the page is up on the wiki.
Link: http://projects.scipy.org/scipy/scipy/wiki/PeriodicTable
Thanks for putting that up Adam. It all looks pretty good so far, but the following caught my eye:
* All temperatures should be in Celsius. Conversions will be performed by methods (or a package in scipy, if scipy has a unit conversion system)
Would it not be better to work in units of Kelvin? In my experience Kelvin is used more often than Celcius in scientific work. What do others think?
I agree, Kelvin would be the most natural choice. Plenty of thermodynamics calculations demand temperature be in units of Kelvin. Darren
Kelvin it is then. I'm not very familiar on scientific standards. I guess it -does- make more sense though... Changing that now.
CakeProphet wrote:
I think it would be fairly useful if scipy contained a module with the entire period table as a Python data type of some sort with various information (atomic number, mass, etc) of all the elements.
I've thought about that for years, never taking the time to make it happen. The trick is not just to list the elements in a Python dictionary, with physical attributes, but to provide various filter and search operations -- list all metals, nobel elements, given a weight range return the matching set of elements, handle isotope mapping back to their base elements, etc. Designed and documented well, it would be a neat component. -Jeff
Jeff, this indeed sounds cool. Kind of a *naturally organized* data framework for atomic, spectral, and other data. Kind of atomic google? Going on with your impressive list, does it make sense to integrate into the search engine a computational engine to *compute missing data*? E.g., atomic/spectral physics engine to compute intensities for spectral transitions using the run-time computed wavefunctions, and/or the neural network engine/estimator (based on available data). cheers, val ----- Original Message ----- From: "Jeff Rush" <jeff@taupro.com> To: "SciPy Developers List" <scipy-dev@scipy.org> Sent: Sunday, December 17, 2006 2:08 AM Subject: Re: [SciPy-dev] Period table?
CakeProphet wrote:
I think it would be fairly useful if scipy contained a module with the entire period table as a Python data type of some sort with various information (atomic number, mass, etc) of all the elements.
I've thought about that for years, never taking the time to make it happen. The trick is not just to list the elements in a Python dictionary, with physical attributes, but to provide various filter and search operations -- list all metals, nobel elements, given a weight range return the matching set of elements, handle isotope mapping back to their base elements, etc. Designed and documented well, it would be a neat component.
-Jeff _______________________________________________ Scipy-dev mailing list Scipy-dev@scipy.org http://projects.scipy.org/mailman/listinfo/scipy-dev
participants (7)
-
Adam Curtis -
CakeProphet
-
Darren Dale -
Jeff Rush -
Robert Kern -
Tim Leslie -
val