Page 1 of 1

CAMB library file using the w(a) ppf module?

Posted: April 06 2009
by Renee Hlozek
Hi,

I have compiled the dynamical w(a) models in the CAMB Add-ons [from the cross.tar.gz file] and can run CAMB from the command line correctly, but am having trouble when I make all to get a libcamb.a library for use in another code... is there anything obvious I am missing - or does the new library know that there will be new fields for w_0 , w_a specified?
cheers
Renee

CAMB library file using the w(a) ppf module?

Posted: April 09 2009
by Ivan Debono
I think I've encountered a related problem. Tried to use the ppf modules with a CAMB Fisher matrix code, and they won't work, even if I can use them when I run CAMB from the command line.

Re: CAMB library file using the w(a) ppf module?

Posted: April 27 2009
by Wenjuan Fang
Renee Hlozek wrote:Hi,

I have compiled the dynamical w(a) models in the CAMB Add-ons [from the cross.tar.gz file] and can run CAMB from the command line correctly, but am having trouble when I make all to get a libcamb.a library for use in another code... is there anything obvious I am missing - or does the new library know that there will be new fields for w_0 , w_a specified?
cheers
Renee

The library should know about the w_0, w_a parameterization, because equations.f90 is modified to do so. Since new input parameters, like `usew0wa', are introduced in the modification, perhaps you need to be more careful when writing your own driver code and parameter file.

CAMB library file using the w(a) ppf module?

Posted: July 17 2009
by Renee Hlozek
The problem was when I tried to call ppf from another module (a Fisher matrix code). I had edited the Makefile to use the new files such as equations_cross.f90 instead of the standard files. However, the Fisher code that needed the library was looking for object files with the original names.

Once I renamed the files as equations.f90 etc.. things worked out correctly and I can now call the library externally.

Another thing to remember of course is that the variable types (such as usew0wa) are defined correctly in the external code.