NorCPM User Manual - Revision history

Retish at 15:01, 3 December 2014

2014-12-03T15:01:45Z

← Older revision		Revision as of 15:01, 3 December 2014
Line 76:		Line 76:
	:''cd NorESM''		:''cd NorESM''

	If you have a ~~NoreSM~~ svn access do:		If you have a NorESM svn access do:

	:''svn checkout https://svn.met.no/NorESM/noresm/tags/projectEPOCASA-3 projectEPOCASA-3''		:''svn checkout https://svn.met.no/NorESM/noresm/tags/projectEPOCASA-3 projectEPOCASA-3''

Retish at 15:01, 3 December 2014

2014-12-03T15:01:04Z

← Older revision		Revision as of 15:01, 3 December 2014
Line 85:		Line 85:

	:''mkdir -p Script''		:''mkdir -p Script''

			:''cd Script''

	In order to use the default Script version		In order to use the default Script version

Francois at 14:46, 7 November 2014

2014-11-07T14:46:13Z

← Older revision		Revision as of 14:46, 7 November 2014
Line 271:		Line 271:
	Then you need to edit ${HOME}/NorESM/Script/personal_setting.sh:		Then you need to edit ${HOME}/NorESM/Script/personal_setting.sh:
	:adjust the start_date accordingly		:adjust the start_date accordingly
	:set RFACTOR=1 (no need to slow ~~aswim~~ start)		:set RFACTOR=1 (no need to slow assim start)
	:skip the first assimilation SKIPASSIM=0 (the restart file in archive have already been assimilated)		:skip the first assimilation SKIPASSIM=0 (the restart file in archive have already been assimilated)

Line 279:		Line 279:
	Launchin prediction is quite simple. '''We are using the same ensemble structure, so make sure that all file in archive folder are back-up before starting that.'''		Launchin prediction is quite simple. '''We are using the same ensemble structure, so make sure that all file in archive folder are back-up before starting that.'''

	*First,''${HOME}/NorESM/Script/mv_rst_from_archive_to_run.sh date_to_restart''		*First, you may launch ''${HOME}/NorESM/Script/mv_rst_from_archive_to_run.sh date_to_restart''
	*Second, ''${HOME}/NorESM/Script/change_running_freq_4_prediction.sh'' ~~this~~ will set the setting of NorESM to integrate for 10 years instead of a month.		*Second, ''${HOME}/NorESM/Script/change_running_freq_4_prediction.sh''.

			This will set the setting of NorESM to integrate for 10 years instead of a month.
	Remember that you will need to change back to monthly frequency if you want to run a REANAYLSIS		Remember that you will need to change back to monthly frequency if you want to run a REANAYLSIS
	*Third Submit the super-job (that will integrate your whole ensemble):		*Third Submit the super-job (that will integrate your whole ensemble):
	:''qsub Integrate_ens_predict.sh''		:''qsub Integrate_ens_predict.sh''

	=== Reduction and ~~Compression~~ of outputs ===		=== Reduction and compression of outputs ===
	The amount of storage produced by ensemble run, and it is needed to try to reduce it as much as possible before starting backing up the data.		The amount of storage produced by ensemble run is huge and it is needed to try to reduce it as much as possible before starting backing up the data.
	It is recommended to ~~proceed with that~~ regularly while you are progressing with your reanalysis. As such you are sure that you keeping the work usage low.		It is recommended to repeat this step regularly while you are progressing with your reanalysis (every 2 days ?). As such you are sure that you keeping the work usage low and make sure that you do not lose it due to automatic deletion.
	~~After~~ you are finished with reducing and compressing you can proceed with ~~backing up~~ the data to for example NORSTORE.		Once you are finished with reducing and compressing, you can proceed with the transfert of the data to the backup folder (see following section for example NORSTORE).
	~~This should be done in~~ two ~~step~~:
	:*First, ~~try to~~ only ~~retain~~ file that you ~~are~~ really ~~going~~ to use. There is currently a script called Reduce_Exp_size.sh that only keep: 4 restart per year, ocean monthly average file, h0 output for atmosphere and land.		In order to reduce and compress follow the two steps:
	:*Second,~~After running the previous step you can~~ convert the output from netcd3 to netcdf4 ~~(this will save approximately 50% of output)~~ and zip ensemble of restart file together. The conversion is done in parallel and should be launched to the queue as follow:		:*First, retain only file that you really need to use. There is currently a script called Reduce_Exp_size.sh that only keep: 4 restart per year, ocean monthly average file, h0 output for atmosphere and land.
			:*Second, convert the output from netcd3 to netcdf4 and zip ensemble of restart file together (it would reduce the size by more than 50%). The conversion is done in parallel and should be launched to the queue as follow:

	::''qsub noresm2netcdf4.pbs''		::''qsub noresm2netcdf4.pbs''
Line 298:		Line 301:

	=== Archiving to NorStore ===		=== Archiving to NorStore ===
	NorStore is a machine in Oslo that provides storage facility. Via EPOCASA project we do have 10 TB of storage on disk and 10 TB of storage on tape.		NorStore is a machine in Oslo that provides storage facility. Via EPOCASA project we do have so far 10 TB of storage on disk and 10 TB of storage on tape.
	In order to loging to norstore, we are recommending to do so via login3:		In order to loging to norstore, we are recommending to do so via login3:
	::''ssh -Y login3.norstore.uio.no'		::''ssh -Y login3.norstore.uio.no''

	==== Disk storage ====		==== Disk storage ====

Francois at 14:38, 7 November 2014

2014-11-07T14:38:42Z

← Older revision		Revision as of 14:38, 7 November 2014
Line 227:		Line 227:
	You have a lot of data assimilation parameter in :		You have a lot of data assimilation parameter in :
	''/work/shared/nn9039k/NorCPM/Input/EnKF/enkf.prm_mal''		''/work/shared/nn9039k/NorCPM/Input/EnKF/enkf.prm_mal''
	*method ~~of assimilation~~ you can chose between EnKF and DENKF. The first ~~was~~ is a stochastic filter and the other is a deterministic filter i.e. that it does not perturb observation (See Sakov et al. 2008 for a more thoroughly description).		:*''method'': you can chose between EnKF and DENKF. The first is a stochastic filter and the other is a deterministic filter i.e. that it does not perturb observation (See Sakov et al. 2008 for a more thoroughly description).
	*ensemble contain the ensemble size ('''TODO make that it matches automatically size of personal setting!!''')
	*Localisation is a critical parameter of assimilation. It is an ad-hoc way to limit the impact of observation as a function of the distance to the model grid point. A model grid point ould only be influenced by obs found within the localisation radius (locrad in the prm file and is in km). The larger you localisation radius is the higher degree of freedom you have in your model and the larger the number of member you would need to span it properly.The optimal localisation radius depends on your ensemble size. In NorCPM we are currently only considering single water column update (i.e. locfuntag = "STEP" and locrad = 95). If you want to see the impact of increasing the localisation radius, you can for example use locfuntag = "G&C" and locrad = 600 . Note that the G&C means that the influence will be reduced as a function of the distance by tapering (schur product). 600 km would give an effective radius of ~200 km.		:*''ensemble'': contain the ensemble size ('''TODO make that it matches automatically size of personal setting!!''')
	* ~~You also have possibility~~ to ~~play with moderation~~:
			:*''Localisation'': is a critical parameter of assimilation. It is an ad-hoc way to limit the impact of observation as a function of the distance to the model grid point. A model grid point ould only be influenced by obs found within the localisation radius (locrad in the prm file and is in km). The larger you localisation radius is the higher degree of freedom you have in your model and the larger the number of member you would need to span it properly.The optimal localisation radius depends on your ensemble size. In NorCPM we are currently only considering single water column update (i.e. locfuntag = "STEP" and locrad = 95). If you want to see the impact of increasing the localisation radius, you can for example use locfuntag = "G&C" and locrad = 600 . Note that the G&C means that the influence will be reduced as a function of the distance by tapering (schur product with a Gaussian distribution). A radius of 600 km would would give an effective radius of ~200 km.
			*''moderation'' all made to avoid excessive reducing of ensemble spread:
	**inflation is a way to artificially inflate you ensemble spread (multiplicative covariance inflation)		**inflation is a way to artificially inflate you ensemble spread (multiplicative covariance inflation)
	**rfactor1 is the way to do a slow assimilation start (It is handle automatically by the main script of the reanalysis		**rfactor1 is the way to do a slow assimilation start (It is handle automatically by the main script of the reanalysis
Line 241:		Line 243:
	*Here you can also estimate model output by state augmentation (you can estimate evolving model bias as well)		*Here you can also estimate model output by state augmentation (you can estimate evolving model bias as well)

	=== Running the ~~system~~ ===		=== Running the Analysis ===
	The system must be running on the login node.		The system must be running on the login node.
	it is run by the command:		it is run by the command:
Line 248:		Line 250:
	:''screen''		:''screen''
	:''${HOME}/NorESM/Script/main.sh''		:''${HOME}/NorESM/Script/main.sh''
	:''ctrl+a+d~~" (~~to quit the screen"		:''ctrl+a+d ''to quit the screen''
	:"screen -r" (to reattach it)		:''screen -r'' (to reattach it)
	Note that there are 5 available login node on hexagon. Your screen would be only available from the screen you launch it from.		Note that there are 5 available login node on hexagon. Your screen would be only available from the screen you launch it from.
	To change from one login node to the other, simply type:		To change from one login node to the other, simply type:
	:''ssh login1" (to access the first login node)		:''ssh login1" (to access the first login node)

	=== How to restart if it ~~crashes~~ ===		You can check then the progress of your job by looking at the files produced in ''/work/${USER}/archive/'' folder or in ''/work/${USER}/RESULT/''. You can check if your system is still alive by checking the queue (qstat) now and then or reattaching the screen.

			=== How to restart your reanalysis if it stop ? ===
	The system is quite robust, but some crashes may happen (power outage, fork issue, machine slow so that wall time is reached ....)		The system is quite robust, but some crashes may happen (power outage, fork issue, machine slow so that wall time is reached ....)
	It is good if you can identify depending on where the system stop (the last line on your screen).
			It is good if you can identify depending on where the system stop (indicated by the last line on your screen).

	You can then start edit ${HOME}/NorESM/Script/personal_setting.sh and restart from the start_date and the place in the code you want (playing with SKIPASSIM and SKIPPROP)		You can then start edit ${HOME}/NorESM/Script/personal_setting.sh and restart from the start_date and the place in the code you want (playing with SKIPASSIM and SKIPPROP)

Francois at 14:30, 7 November 2014

2014-11-07T14:30:26Z

← Older revision		Revision as of 14:30, 7 November 2014
Line 218:		Line 218:
	Examples:		Examples:

	:''temp 1 53'' means that we update temperature for layer 1 to 53. Note that in MICOM, there are 2 time level for each variable (leap frog). If you model has kdm vertical level, first time level is 1:kdm while the second is kdm+1:2kdm		:''temp 1 53'': means that we update temperature for layer 1 to 53. Note that in MICOM, there are 2 time level for each variable (leap frog). If you model has kdm vertical level, first time level is 1:kdm while the second is kdm+1:2kdm
	:*''pb 1 1'' means that we only update the first vertical level (pb is a variable with only the two time level)		:*''pb 1 1'': means that we only update the first vertical level (pb is a variable with only the two time level)
	:*''ustar 0 0'' means that the variable is only 2d and there is no 3rd dimension		:*''ustar 0 0'': means that the variable is only 2d and there is no 3rd dimension

Francois at 14:29, 7 November 2014

2014-11-07T14:29:27Z

← Older revision		Revision as of 14:29, 7 November 2014
Line 129:		Line 129:
	:''${HOME}/NorESM/Script/cleanup_single_mem.sh 1''		:''${HOME}/NorESM/Script/cleanup_single_mem.sh 1''
	this would delete member 1		this would delete member 1

	~~=== How to start your ensemble from a non pre-existing initial ensemble ===~~
	~~You have two existing set up one for NorCPM_ME and one for NorCPM_F19_tn21 both for 1980-01-15. This initial restart are in /work/shared and are automatically retrieved by create_esemble.sh.~~
	~~If you want to start from a different start date, this is slightly more complicated. There are up to now two different strategy:~~

	:*The first is to restart from an existing ensemble (historical or preindustriel). NorESM beeing very rigid you won't be able to directly restart from the ensemble is there is any slight difference in the model version, in the file name or in dianostic of the output. You need to do a hybrid start. In personal_setting.sh you should have set hybrid_run=1 and ens_start=1. You need to specify the existing ens_casename and wished start date.

	:*The second option is an historical start. It is possible to start your ensemble from a single run. It is recommended to use a run that is run with pre-industrial focing because if not your initial ensemble may contain spurious correlation induced by the drift of the system with historical anthropogenic forcing. To run this option, set hybrid_run=1, ens_start=0, hist_start=1, hist_path hist_start_date and hist_freq_date. This is not tested in the new script system and most of the code is commented out, but it should be only minor edit to update the code. Contact us if you have question. The best approach is then to run your ensemble with historical forcing up to the wished starting date.

	In the current NorCPM we are assimilating data at monthly frequency. As data is centered in the middle of the month, it is best to assimilate data in the middle of the months. When you are make a hybrid start from an run, monst of the time retsart are available at the beginning of a year/month. One need to integrate the ensemble for half a month before starting the system. To do so you must change running frequency to 14 days in ens_run.xml. For doing so, you can use the script : ''Integrate_ens_half-month.sh''

	~~When the integration is finished you need to set the frequency back to monthly. this can be done with ''change_running_freq_4_analysis.sh''~~


Line 167:		Line 155:

	The folder ''cases'' contains setting of your ensemble of experiment. Each ensemble members have its own separate experiment subfolder (duplicate files are linked to reduce the disk usage).		The folder ''cases'' contains setting of your ensemble of experiment. Each ensemble members have its own separate experiment subfolder (duplicate files are linked to reduce the disk usage).

			=== How to start your ensemble from a non pre-existing initial ensemble ===
			Nowadays, you have two existing set up: one with NorCPM_ME and one with NorCPM_F19_tn21 both which are both starting on the 1980-01-15. This initial restart are in /work/shared and are automatically retrieved by create_esemble.sh.
			If you want to start from a different start date, this is slightly more complicated. There are currently two different strategy implemented:

			:*The first is to restart from an existing ensemble (historical or preindustriel). NorESM beeing very rigid you won't be able to directly restart from the ensemble is there is any slight difference in the model version, in the file name or in dianostic of the output. You need to use a hybrid start. In personal_setting.sh you should have set ''hybrid_run''=1 and ''ens_start''=1. You need to specify the existing ens_casename and wished start date.

			:*The second option is an historical start. It is possible to start your ensemble from a single run. It is recommended to use a run that is run with pre-industrial foxing, otherwise your initial ensemble may contain spurious correlation induced by the drift of the system with historical anthropogenic forcing. To run this option, set ''hybrid_run''=1, ''ens_start''=0, ''hist_start''=1, ''hist_path'', ''hist_start_date'' and ''hist_freq_date''. This is not tested in the new script system and most of the code is commented out, but it should be only minor edit to update the code. Contact us if you have question. The best approach is then to run your ensemble with historical forcing up to the wished starting date.

			In the current NorCPM we are assimilating data at monthly frequency. As data is centered in the middle of the month, it is best to assimilate data in the middle of the months. When you are making a hybrid start from an run, the time stamp of the restart would likely be the beginning of a year/month. One need to integrate the ensemble for half a month before starting the system. To do so you must change running frequency to 14 days in ens_run.xml. For doing so, you can use the script : ''Integrate_ens_half-month.sh''

			When the integration is finished you need to set the frequency back to monthly. this can be done with ''change_running_freq_4_analysis.sh''




	=== Option available in NorCPM (in personal_setting.sh) ===		=== Option available in NorCPM (in personal_setting.sh) ===
Line 178:		Line 181:
	:-''NorCPM_ME'' (or f19_g16) is the medium resolution used for CMIP5: It uses CAM-OSLO at a resolution of F19 for the atmosphere (about 2 dergree resolution) and about 1 degree for the ocean (bipolar grid).		:-''NorCPM_ME'' (or f19_g16) is the medium resolution used for CMIP5: It uses CAM-OSLO at a resolution of F19 for the atmosphere (about 2 dergree resolution) and about 1 degree for the ocean (bipolar grid).

			Assimilation of multiple type of observation is not yet available.
	About the type of observation available is OBSTYPE=SST and PRODUCER='HADISST2' (reynolds is also possible)~~. Assimilation of multiple type of observation is not yet available~~.		About the type of observation available is OBSTYPE=SST and PRODUCER=''HADISST2'' (reynolds is also possible).

	You need to decide when your experiment will start and when it will finish (start_date and ENDYEAR)		You need to decide when your experiment will start and when it will finish (start_date and ENDYEAR)
Line 185:		Line 188:
	You can chose how many member (ensemble size) you want to use. Beware that if you want to use too few members, EnKF would perform badly (don't even try with 1 or 2 ).		You can chose how many member (ensemble size) you want to use. Beware that if you want to use too few members, EnKF would perform badly (don't even try with 1 or 2 ).

	For NorCPM_F19_tn21 and NorCPM_ME there is already an initial ensemble for 1980-01-15 for other starting date you need a more complex manover as detailled in ~~XXX-~~		For NorCPM_F19_tn21 and NorCPM_ME there is already an initial ensemble for 1980-01-15 for other starting date you need a more complex manover as detailled in following section.


Line 191:		Line 194:
	==== Setting of the assimilation ====		==== Setting of the assimilation ====
	You have different option available. First you may decide if you would like to use Anomaly assimilation or full field assimilation.		You have different option available. First you may decide if you would like to use Anomaly assimilation or full field assimilation.
	~~This~~ is ~~done when~~ compiling the ~~EnKF code~~		Note that anomaly assimilation is available by default so if you want to use full fill you need to compile EnKF and prep_obs and replace the link in your ${HOME}/NorESM/bin/ by the updated executable.
	define the FLAG ANOMALY ~~before compilation~~ in :
			Before compiling the two executable define the FLAG ANOMALY in :
	*''/work/shared/nn9039k/NorCPM/Code/EnKF-MPI-TOPAZ/MODEL.CPP''		*''/work/shared/nn9039k/NorCPM/Code/EnKF-MPI-TOPAZ/MODEL.CPP''
	*''/work/shared/nn9039k/NorCPM/Code/EnKF-MPI-TOPAZ/Prep_Routines/MODEL.CPP''		*''/work/shared/nn9039k/NorCPM/Code/EnKF-MPI-TOPAZ/Prep_Routines/MODEL.CPP''

			Same masking of the land neighbour ons are used by default in the version of work shared so compile your own version if you don't want this option.

	To reject observations near the coast, define the FLAG MASK_LANDNEIGHBOUR in:		To reject observations near the coast, define the FLAG MASK_LANDNEIGHBOUR in:
Line 207:		Line 213:
	You can edit the list of variable that assimilation will update (via linear relation):		You can edit the list of variable that assimilation will update (via linear relation):
	/work/shared/nn9039k/NorCPM/Input/EnKF/analysisfields.in		/work/shared/nn9039k/NorCPM/Input/EnKF/analysisfields.in
	~~Each line describe a model field to be updated:~~

	If the variable ~~is 3D~~ (x,~~y,z)~~ the ~~number indicates~~ the ~~layer~~ (~~in z~~) that ~~we are updating.~~		Each line describe the number of 2D fields that we are updating for each variable.

			Examples:

			:''temp 1 53'' means that we update temperature for layer 1 to 53. Note that in MICOM, there are 2 time level for each variable (leap frog). If you model has kdm vertical level, first time level is 1:kdm while the second is kdm+1:2kdm
			:*''pb 1 1'' means that we only update the first vertical level (pb is a variable with only the two time level)
			:*''ustar 0 0'' means that the variable is only 2d and there is no 3rd dimension

Francois at 14:04, 7 November 2014

2014-11-07T14:04:22Z

← Older revision		Revision as of 14:04, 7 November 2014
Line 66:		Line 66:
	You can go to the following Section Cleanup Ensemble to get a description of how to do that.		You can go to the following Section Cleanup Ensemble to get a description of how to do that.

	~~on your account~~, follow the step:		On hexagon, follow the step:

	1) install NorESM and link the script necessary :		1) install NorESM and link the script necessary :
Line 80:		Line 80:
	:''svn checkout https://svn.met.no/NorESM/noresm/tags/projectEPOCASA-3 projectEPOCASA-3''		:''svn checkout https://svn.met.no/NorESM/noresm/tags/projectEPOCASA-3 projectEPOCASA-3''

	if you don't do:		if you don't:

	:''tar -xvf /work-common/shared/nn9039k/NorCPM/Code/NorESM/projectEPOCASA-3.tar.gz''		:''tar -xvf /work-common/shared/nn9039k/NorCPM/Code/NorESM/projectEPOCASA-3.tar.gz''
Line 120:		Line 120:

	=== Cleanup Ensemble ===		=== Cleanup Ensemble ===
	There is many situation where it is necessary to restart from scratch.		There is many situation where it is necessary to restart from scratch. Before you start clean up everything, make sure that you have backup everything you needed.
	The most obvious is if you want to change model version or that you want to use the same casename for a different model set up. You may also want to free some space on your home directory.		The most obvious is if you want to change model version or that you want to use the same casename for a different model set up. You may also want to free some space on your home directory.
	In all this cases you can delete all file that you have in your work and HOME dire by running the following command.		In all this cases you can delete all file that you have in your work and HOME dire by running the following command.

Francois at 13:56, 7 November 2014

2014-11-07T13:56:18Z

← Older revision		Revision as of 13:56, 7 November 2014
Line 49:		Line 49:

	=== Ensemble Kalman Filter ===		=== Ensemble Kalman Filter ===
	The EnKF is a sequential ensemble based data assimilation method that consists of two steps, a propagation and a correction. The propagation step is a Monte Carlo method. The ensemble spread (i.e. ensemble variability) is used to estimate the forecast error, because they are expected to be related in locations (and times) where (and when) the system is more chaotic. Assuming that the distribution of the error is Gaussian and the model is not biased one can proceed with the tBayesian update and find new estimate of the ensemble mean and model covariance. The method is often called as flow dependent as the covariance matrix evolves with the system and thus provide correction that are in agreement with the state of the system. The method allows fully multivariate updated - meaning that observation of for example SST can be used to apply correction on all other model variables. However one should bear in mind that the update assume linearity, which is not suitable for all variable and that correlation are subject to sampling error. Currently NorCPM uses the Deterministic Ensemble Kalman Filter (DEnKF, Sakov et al. 2008), which is a square root filter version of the EnKF.		The EnKF is a sequential ensemble based data assimilation method that consists of two steps, a propagation and a correction. The propagation step is a Monte Carlo method. The ensemble spread (i.e. ensemble variability) is used to estimate the forecast error, because they are expected to be related in locations (and times) where (and when) the system is more chaotic. Assuming that the distribution of the error is Gaussian and the model is not biased one can proceed with the tBayesian update and find new estimate of the ensemble mean and model covariance. The method is often called as flow dependent as the covariance matrix evolves with the system and thus provide correction that are in agreement with the state of the system. This property is quite valuable for our application because such framework is very suitable for predicting extreme event or for system that are drifting with time. The method also allows for fully multivariate updated, meaning that observation (of for example SST) can be used to apply correction on all other model variables. This is also a valuable properties because observation are very sparse in space and time. However one should bear in mind that the update assume linearity, which is not suitable for all variable and that correlation are subject to sampling error. Currently NorCPM uses the Deterministic Ensemble Kalman Filter (DEnKF, Sakov et al. 2008), which is a square root filter version of the EnKF.
	== Getting started with NorCPM ==		== Getting started with NorCPM ==

Line 63:		Line 63:
	=== Installing compiling NorCPM ===		=== Installing compiling NorCPM ===
	Before installing NorCPM you must be sure that you don't have an old set up already existing.		Before installing NorCPM you must be sure that you don't have an old set up already existing.
	The following script should stop you from completing installation ~~over~~ a conflicting one~~, but still,~~ it is ~~best~~ to cleanup first your experiment.		The following script should stop you from completing a new installation if there is a conflicting one. However it is a good habit to cleanup first your experiment.
	You can go to the following Section Cleanup Ensemble to get a description of how to do that.		You can go to the following Section Cleanup Ensemble to get a description of how to do that.

Francois at 13:38, 7 November 2014

2014-11-07T13:38:53Z

← Older revision		Revision as of 13:38, 7 November 2014
Line 7:		Line 7:

	== Overview ==		== Overview ==
	The Norwegian Climate Prediction Model (NorCPM) is aiming at providing prediction from seasonal-to-decadal time scale. It is based on the Norwegian Earth System Model (NorESM, [https://wiki.met.no/noresm/start]) and the Ensemble Kalman Filter (EnKF, [http://en.wikipedia.org/wiki/Ensemble_Kalman_filter]) data assimilation method. NorESM is a state of the art Earth system model that is based on CESM ([http://en.wikipedia.org/wiki/Community_Climate_System_Model]), but uses different aerosol/chemistry scheme and ocean model (evolved from MICOM). The EnKF is a sequential data assimilation method that allows for fully multivariate and flow dependent correct using a covariance matrix procuded by a Monte-Carlo ensemble integration.		The Norwegian Climate Prediction Model (NorCPM) is aiming at providing prediction from seasonal-to-decadal time scale. It is based on the Norwegian Earth System Model (NorESM, [https://wiki.met.no/noresm/start]) and the Ensemble Kalman Filter (EnKF, [http://en.wikipedia.org/wiki/Ensemble_Kalman_filter]) data assimilation method. NorESM is a state of the art Earth system model that is based on CESM ([http://en.wikipedia.org/wiki/Community_Climate_System_Model]), but uses different aerosol/chemistry scheme and ocean model (evolved from MICOM). The EnKF is a sequential data assimilation method that allows for fully multivariate and flow dependent correct using a covariance matrix procuded by a Monte-Carlo ensemble integration. Currently the system only intend to update the ocean part as this is where most of the predictability is expected, but additional atmospheric nudging and assimilation of land variables are also considered.

	=== Norwegian Earth System Model ===		=== Norwegian Earth System Model ===

Francois at 13:37, 7 November 2014

2014-11-07T13:37:13Z

← Older revision		Revision as of 13:37, 7 November 2014
Line 7:		Line 7:

	== Overview ==		== Overview ==
	The Norwegian Climate Prediction Model (NorCPM) is aiming at providing prediction from seasonal-to-decadal time scale. It is based on the Norwegian Earth System Model (NorESM, [https://wiki.met.no/noresm/start]) and the Ensemble Kalman Filter (EnKF, [http://en.wikipedia.org/wiki/Ensemble_Kalman_filter]) data assimilation method. NorESM is a state of the art Earth system model that is based on CESM ([http://en.wikipedia.org/wiki/Community_Climate_System_Model]), but uses different ~~Aerosol~~/chemistry scheme and ocean model ( ~~evolve~~ from ~~the~~ MICOM). The EnKF is a sequential data assimilation method that allows for fully multivariate and flow dependent correct using ~~the~~ covariance matrix ~~from~~ a Monte-~~carlo model~~ integration.		The Norwegian Climate Prediction Model (NorCPM) is aiming at providing prediction from seasonal-to-decadal time scale. It is based on the Norwegian Earth System Model (NorESM, [https://wiki.met.no/noresm/start]) and the Ensemble Kalman Filter (EnKF, [http://en.wikipedia.org/wiki/Ensemble_Kalman_filter]) data assimilation method. NorESM is a state of the art Earth system model that is based on CESM ([http://en.wikipedia.org/wiki/Community_Climate_System_Model]), but uses different aerosol/chemistry scheme and ocean model (evolved from MICOM). The EnKF is a sequential data assimilation method that allows for fully multivariate and flow dependent correct using a covariance matrix procuded by a Monte-Carlo ensemble integration.

	=== Norwegian Earth System Model ===		=== Norwegian Earth System Model ===