Is your feature request related to a problem? Please describe.
I have now seen a couple of cases where users have been thinking that setPheno() will give them the same pheno, wich of course will not happen due to the random error.
Describe the solution you'd like
Maybe renaming (or aliasing) setPheno() to simPheno() would be more didactic approach?
Describe alternatives you've considered
By aliasing and suggesting use of simPheno() instead of setPheno() the older code would not break.
Additional context
We could then look into making simPheno() a generic function with various model extensions in the future ...
Is your feature request related to a problem? Please describe.
I have now seen a couple of cases where users have been thinking that
setPheno()will give them the same pheno, wich of course will not happen due to the random error.Describe the solution you'd like
Maybe renaming (or aliasing)
setPheno()tosimPheno()would be more didactic approach?Describe alternatives you've considered
By aliasing and suggesting use of
simPheno()instead ofsetPheno()the older code would not break.Additional context
We could then look into making
simPheno()a generic function with various model extensions in the future ...