Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XRMC: new device radionuclide #22

Merged
merged 4 commits into from
Jul 1, 2014
Merged

XRMC: new device radionuclide #22

merged 4 commits into from
Jul 1, 2014

Conversation

tschoonj
Copy link
Collaborator

Hi Bruno,

I have created a new device that inherits from spectrum: now one can define a spectrum using the name of an X-ray producing radionuclide (like "55Fe"), its activity and unit of activity.
This is possible through a couple of new functions I added to xraylib: I am offering support for 10 commonly used radionuclides:

55 Fe
238 Pu
244 Cm
109 Cd
125 I
241 Am
153 Gd
57 Co
133 Ba
137 Cs

So for this to work, you will need to use the development version of xraylib (branch nuclide-data, will merge it later into master).

Ciao ciao,

Tom

@golosio golosio merged commit a41bb8e into golosio:master Jul 1, 2014
@golosio
Copy link
Owner

golosio commented Jul 1, 2014

Dear Tom,
sorry for not answering before, but I have some problem with xrmc/xraylib
if I try to compile xrmc, I get an error
configure: error: Package requirements (libxrl >= 3.1.0) were not met:

Requested 'libxrl >= 3.1.0' but version of xraylib is 3.0.0
If I try to update xraylib:
git pull
Already up-to-date.

git status
On branch master
Your branch is ahead of 'origin/master' by 4 commits.
(use "git push" to publish your local commits)

nothing to commit, working directory clean

xraylib
xraylib 3.0.0 revised February 2014
if it is up to date, why do I have v3.0.0 and not v.1.0?
Thank you, bruno

On 06/25/2014 06:55 PM, Tom Schoonjans wrote:

Hi Bruno,

I have created a new device that inherits from spectrum: now one can
define a spectrum using the name of an X-ray producing radionuclide
(like "55Fe"), its activity and unit of activity.
This is possible through a couple of new functions I added to xraylib:
I am offering support for 10 commonly used radionuclides:

55 Fe
238 Pu
244 Cm
109 Cd
125 I
241 Am
153 Gd
57 Co
133 Ba
137 Cs

So for this to work, you will need to use the development version of
xraylib (branch nuclide-data, will merge it later into master).

Ciao ciao,

Tom


    You can merge this Pull Request by running

git pull https://github.com/tschoonj/xrmc master

Or view, comment on, or merge it at:

#22

    Commit Summary


Reply to this email directly or view it on GitHub
#22.


Dr. Bruno Golosio
Università degli Studi di Sassari, Dipartimento PolComIng,
Sezione di Ingegneria Informatica, Istituto di Matematica e Fisica
via Piandanna 4, 07100 Sassari
Tel +39 079 229587 Fax +39 079 229482

@tschoonj
Copy link
Collaborator Author

tschoonj commented Jul 1, 2014

Hi Bruno,

You will first have to bring your xraylib fork up to date with my repository.

Do something like;

git pull tom master

or

git pull upstream master

I think one of these should work, if not the have a look at the .git/config file in your xraylib tree: there should be the correct reference to my repository (it has tschoonj in its name)

After doing this, run autoreconf and run configure, make and sudo make install again. Then you should be able to reinstall xrmc

Let me know if you need further assistance.

Ciao,

Tom

Op 1-jul.-2014, om 07:44 heeft golosio notifications@github.com het volgende geschreven:

Dear Tom,
sorry for not answering before, but I have some problem with xrmc/xraylib
if I try to compile xrmc, I get an error
configure: error: Package requirements (libxrl >= 3.1.0) were not met:

Requested 'libxrl >= 3.1.0' but version of xraylib is 3.0.0
If I try to update xraylib:
git pull
Already up-to-date.

git status
On branch master
Your branch is ahead of 'origin/master' by 4 commits.
(use "git push" to publish your local commits)

nothing to commit, working directory clean

xraylib
xraylib 3.0.0 revised February 2014
if it is up to date, why do I have v3.0.0 and not v.1.0?
Thank you, bruno

On 06/25/2014 06:55 PM, Tom Schoonjans wrote:

Hi Bruno,

I have created a new device that inherits from spectrum: now one can
define a spectrum using the name of an X-ray producing radionuclide
(like "55Fe"), its activity and unit of activity.
This is possible through a couple of new functions I added to xraylib:
I am offering support for 10 commonly used radionuclides:

55 Fe
238 Pu
244 Cm
109 Cd
125 I
241 Am
153 Gd
57 Co
133 Ba
137 Cs

So for this to work, you will need to use the development version of
xraylib (branch nuclide-data, will merge it later into master).

Ciao ciao,

Tom


You can merge this Pull Request by running

git pull https://github.com/tschoonj/xrmc master

Or view, comment on, or merge it at:

#22

Commit Summary

  • included XMI-MSIM 4.0 requirement in NSIS files
  • support for XMI-MSIM 4.0/new manual
  • new device: radionuclide
  • radionuclide example build fix

File Changes

Patch Links:


Reply to this email directly or view it on GitHub
#22.


Dr. Bruno Golosio
Università degli Studi di Sassari, Dipartimento PolComIng,
Sezione di Ingegneria Informatica, Istituto di Matematica e Fisica
via Piandanna 4, 07100 Sassari
Tel +39 079 229587 Fax +39 079 229482

Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants