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

New function 'model_SampleHistory()' to separate modelling of burial history from (SAR) measurement #8

Open
tzerk opened this issue Jul 28, 2016 · 2 comments

Comments

@tzerk
Copy link
Member

tzerk commented Jul 28, 2016

New function model_SampleHistory():

  • argument model = c("Bailey2001", ..., "Pagonis2007") to determine the quartz model to be used for modelling the sample history
  • argument sequence = list() inheriting the same keywords and syntax as in model_LuminescenceSignals()
  • returning an RLum.Results object that contains the trap/hole concentrations after the last step of the sample history

Modification of model_LuminescenceSignals():

  • argument simulate_samply_history renamed to sample_history (default NULL)
  • if e.g. model = "Bailey2004" and sample_history = NULL the pre-calculated values provided by the package (see .set_Pars()) of the specified model are used
  • alternatively, an RLum.Results object returned from model_SampleHistory can be used for argument sample_history

Advantages:

  • if a user wants to simulate the luminescence signals of sample with a sample history other than the provided ones the sample history has only to be modelled once. This is particularly useful if multiple sequences with changing parameters are used on the same sample history and can save a lot of computation time.
  • different sample histories can be saved in the R workspace
@JohannesFriedrich
Copy link
Collaborator

That's a very good idea because the problem until now is, that you can't use your own sample history and use the SAR-sequence generator.
This enhancement will be part of package 0.2.0.

@RLumSK
Copy link
Member

RLumSK commented Aug 17, 2020

Did this ever become part of the package?

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

No branches or pull requests

3 participants