Git Product home page Git Product logo

Comments (3)

gonuke avatar gonuke commented on May 28, 2024

Hi Matt,

One of the benefits of Cyclus' design is that we don't have to have a
fixed set of isotopes. The user can choose which isotopes to track as
long as they provide sufficient data to support that.

Perhaps a different question is what set of isotopes we will provide
data for in a standard installation.

Paul

On 02/21/2012 01:27 PM, gidden wrote:

@katyhuff Does this already exist somewhere?

At first I went to decayInfo.dat, but that doesn't list any stable isotopes (duh..). Is this list predefined somewhere else or do we need to define it now?

I know other fuel cycle sims group isotopes based on certain characteristics, which we can, of course, do. Just thought we should discuss.


Reply to this email directly or view it on GitHub:
https://github.com/cyclus/core/issues/42

-- ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ --
Paul Wilson ~ UW-Madison ~ 608-263-0807 ~ cal: http://bit.ly/pphw-cal
Associate Professor, Engineering Physics. ~ http://cnerg.engr.wisc.edu
Chair, Energy Analysis& Policy Program ~ http://nelson.wisc.edu/eap

from cyclus.

gidden avatar gidden commented on May 28, 2024

Agreed. I had thought that we kept track of some key isotopes due to decayInfo.day. I instead implemented Roberts suggestion of using a combined primary key of a states id and the isotopes id.

from cyclus.

katyhuff avatar katyhuff commented on May 28, 2024

We currently only have mass references for a finite number of isotopes
(which can be replaced by an interested user) in mass.h5 , which, if we're
migrating away from HDF5, I guess someone may want to convert to something
else to make an option that is not hdf5 dependent available to the user...
Having already converted it to hdf5, I'm not likely to volunteer, but would
be happy to help.

I think your generic solution is the answer. The mass table was a temporary
fix, but was always intended to be user specified.

On Tue, Feb 21, 2012 at 9:19 PM, gidden <
[email protected]

wrote:

Agreed. I had thought that we kept track of some key isotopes due to
decayInfo.day. I instead implemented Roberts suggestion of using a combined
primary key of a states id and the isotopes id.


Reply to this email directly or view it on GitHub:
https://github.com/cyclus/core/issues/42#issuecomment-4085860

http://homepages.cae.wisc.edu/~khuff/

from cyclus.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.