Quintessence
-
- Posts: 28
- Joined: July 18 2013
- Affiliation: University of Oslo
Quintessence
Hey.
I am trying to implement quintessence with the newest COSMOMC and CAMB. But since equations_quint.f90 has not been updated for some time, does it have some problem working with CAMB. Specially with cmbmain.f90.
cmbmain.f90(947): error #6460: This is not a field name that is defined in the encompassing structure. [G_IX]
write (1,'(7E15.5)') tau, delta, growth, y(3), y(4), y(EV%g_ix), y(1)
----------------------------------------------------------------------^
cmbmain.f90(970): error #6633: The type of the actual argument differs from the type of the dummy argument. [TAU]
call output(EV,y,j,tau,sources)
-------------------------------^
cmbmain.f90(970): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface. [SOURCES]
call output(EV,y,j,tau,sources)
-----------------^
cmbmain.f90(970): error #6634: The shape matching rules of actual arguments and dummy arguments have been violated. [SOURCES]
call output(EV,y,j,tau,sources)
-----------------------------------^
cmbmain.f90(1068): error #6404: This name does not have a type, and must have an explicit type. [DERIVSV]
call dverk(EV,EV%nvarv,derivsv,tau,yv,tauend,tol1,ind,c,EV%nvarv,wt) !tauend
-----------------------------------^
compilation aborted for cmbmain.f90 (code 1)
Any suggestion what to do, or if has to do with the different variables which is on defined everywhere. Most probably because of newer versions. Any help is received greatfully.
I am trying to implement quintessence with the newest COSMOMC and CAMB. But since equations_quint.f90 has not been updated for some time, does it have some problem working with CAMB. Specially with cmbmain.f90.
cmbmain.f90(947): error #6460: This is not a field name that is defined in the encompassing structure. [G_IX]
write (1,'(7E15.5)') tau, delta, growth, y(3), y(4), y(EV%g_ix), y(1)
----------------------------------------------------------------------^
cmbmain.f90(970): error #6633: The type of the actual argument differs from the type of the dummy argument. [TAU]
call output(EV,y,j,tau,sources)
-------------------------------^
cmbmain.f90(970): error #6631: A non-optional actual argument must be present when invoking a procedure with an explicit interface. [SOURCES]
call output(EV,y,j,tau,sources)
-----------------^
cmbmain.f90(970): error #6634: The shape matching rules of actual arguments and dummy arguments have been violated. [SOURCES]
call output(EV,y,j,tau,sources)
-----------------------------------^
cmbmain.f90(1068): error #6404: This name does not have a type, and must have an explicit type. [DERIVSV]
call dverk(EV,EV%nvarv,derivsv,tau,yv,tauend,tol1,ind,c,EV%nvarv,wt) !tauend
-----------------------------------^
compilation aborted for cmbmain.f90 (code 1)
Any suggestion what to do, or if has to do with the different variables which is on defined everywhere. Most probably because of newer versions. Any help is received greatfully.
-
- Posts: 1943
- Joined: September 23 2004
- Affiliation: University of Sussex
- Contact:
Re: Quintessence
The version currently on the website should be fairly up to date (2013) and certainly defines g_ix.
http://camb.info/extra.html
http://camb.info/extra.html
-
- Posts: 28
- Joined: July 18 2013
- Affiliation: University of Oslo
Quintessence
Thank you.
It was not long ago that I downloaded the quintessence file, but it works now, but of cource are there now other aspect that does not work. CMB_Cls_simple.f90:
CMB_Cls_simple.f90(5): error #6580: Name in only-list does not exist. [WA_PPF]
AccuracyBoost, Cl_scalar, Cl_tensor, Cl_lensed, outNone, w_lam, wa_ppf,&
---------------------------------------------------------------------^
CMB_Cls_simple.f90(55): error #6404: This name does not have a type, and must have an explicit type. [WA_PPF]
wa_ppf = CMB%wa
----^
CMB_Cls_simple.f90(62): error #6460: This is not a field name that is defined in the encompassing structure. [NU_MASS_SPLITTINGS]
P%Nu_mass_splittings = .true.
----------^
CMB_Cls_simple.f90(62): error #6303: The assignment operation or the binary expression operation is invalid for the data types of the two operands.
P%Nu_mass_splittings = .true.
-------------------------------^
CMB_Cls_simple.f90(89): error #6303: The assignment operation or the binary expression operation is invalid for the data types of the two operands.
P%Nu_mass_splittings = .false.
-------------------------------^
compilation aborted for CMB_Cls_simple.f90 (code 1)
make[1]: *** [CMB_Cls_simple.o] Error 1
Has these also been updated?
It was not long ago that I downloaded the quintessence file, but it works now, but of cource are there now other aspect that does not work. CMB_Cls_simple.f90:
CMB_Cls_simple.f90(5): error #6580: Name in only-list does not exist. [WA_PPF]
AccuracyBoost, Cl_scalar, Cl_tensor, Cl_lensed, outNone, w_lam, wa_ppf,&
---------------------------------------------------------------------^
CMB_Cls_simple.f90(55): error #6404: This name does not have a type, and must have an explicit type. [WA_PPF]
wa_ppf = CMB%wa
----^
CMB_Cls_simple.f90(62): error #6460: This is not a field name that is defined in the encompassing structure. [NU_MASS_SPLITTINGS]
P%Nu_mass_splittings = .true.
----------^
CMB_Cls_simple.f90(62): error #6303: The assignment operation or the binary expression operation is invalid for the data types of the two operands.
P%Nu_mass_splittings = .true.
-------------------------------^
CMB_Cls_simple.f90(89): error #6303: The assignment operation or the binary expression operation is invalid for the data types of the two operands.
P%Nu_mass_splittings = .false.
-------------------------------^
compilation aborted for CMB_Cls_simple.f90 (code 1)
make[1]: *** [CMB_Cls_simple.o] Error 1
Has these also been updated?
-
- Posts: 1943
- Joined: September 23 2004
- Affiliation: University of Sussex
- Contact:
Re: Quintessence
It don't think it has ever been integrated with CosmoMC.
-
- Posts: 28
- Joined: July 18 2013
- Affiliation: University of Oslo
Quintessence
Okey I see. What would be the necessary steps to be able to integrate with CosmoMC? Any suggestions and tips will be great. And thanks for the help so far.