Closed kevinhainline closed 8 years ago
The problem is caused by the use of the option 3
(mock catalogue creation), while some parameters or set to type:fitted
, which is not supported (fitted
parameters can be used with option 1
). You should be consistent when using option 3
and define the parameters following Emma's example, e.g. mock:type:random mock:distribution:uniform mock:range:[-4.,-2.]
.
For the SF_PARAMETER
, you can just look at Sec. 5.1 of the manual: all the parameters listed in that section must be defined using the SF_PARAMETER
keyword instead of the PARAMETER
.
Let me know if this solves!
Actually that's completely my fault! That's the file that I had put up, sorry @kevinhainline - I had never noticed that before and it's interesting that we didn't get an error with it for the previous version! I've just edited the gitHub version to fix it. We still haven't implemented many checks and measures for the parameter file but it's something that we will be doing in the future!
Sorry for that difficulty - but what @jacopo-chevallard wrote is exactly right and should have solved that problem, please let us know if it hasn't.
Closing, since @kevinhainline feedback on #11 suggests that this issue must be considered solved as well
When I run BEAGLE 0.3.0 to see if it works with the mock catalogue generation parameter file originally provided, I get an error message:
At the end of this message you can find the parameter file I was attempting to use. I assume that the error comes about because of the new updates which require me to specify the mock input parameters. In your email, you wrote:
I'm a little confused, why did you write "SF_PARAMETER" for the mass and "PARAMETER" for redshift? Is there a spot in the updated manual where I can read more about this?