Rate not set when running on cluster

[GoogleCodeExporter]

Steps that cause the problem:
1. Run a coded system on the cluster.
2. Try to plot, won't be able to compute Es/No since rate not set in sim_param

Problem is as follows:
The variable sim_param.rate gets set by InitializeCodeParam.
When run locally, this works okay because sim_param.rate gets saved into the 
save file.
However, on the cluster, each task calls InitializeCodeParam but does not save 
sim_param.
So the rate never gets set.

This becomes a problem when trying to plot.

Resolution:
Could set rate either when plotting or when retrieving the cluster job.
Need to make sure other variables are not also affected in this way.

Original issue reported on code.google.com by Matthew....@gmail.com on 12 Mar 2014 at 7:28

[GoogleCodeExporter]

Thanks for the report.  A few clarifications,

- What exactly are the steps referenced by
  1. Run a coded system on the cluster
 For instance, is this using CmlClusterSubmit()
   >>  CmlClusterSubmit(scenario,record)
   >>  CmlClusterRetrieve

- It would be useful to know the exact scenario and record which is exhibiting 
this behavior in order to reproduce the error.

Original comment by terry.fe...@gmail.com on 12 Mar 2014 at 9:11

[GoogleCodeExporter]

Steps are (>> indicates matlab commands; running revision 881):
>> CmlWebSubmit( 'LteRmScenarios', 2)
scp the job file to the JobIn directory on the cluster.
scp the job file from the JobOut directory
>> CmlWebRetrieve
>> CmlPlot( 'LteRmScenarios', 2 )

get the error:
Error using  * 
Inner matrix dimensions must agree.

Error in PlotBerSerCodedUncoded (line 91)
            EsN0 = sim_param_coded(i).rate*EbN0;

Error in CmlPlot (line 70)
    [FigHandle, fig_number] = PlotBerSerCodedUncoded( ...

Further investigation reveals that
sim_param_coded(i).rate = []
so the rate has not been set.

Original comment by Matthew....@gmail.com on 12 Mar 2014 at 9:19

[GoogleCodeExporter]

Attempting to diagnose missing rate parameter in job output.

Try to re-create using scenario/record
  UmtsScenarios/1

Result:
Rate parameter present in job output

Suspect specific behavior of Lte scenario is leading to missing rate.

Dr. Valenti, could you please upload your scenario file containing
   LteRmScenarios 
to the cluster?  Suggest placing it in
   /home/mvalenti/LteRmScenarios.m
I can then attempt to reproduce the issue exactly.

Original comment by terry.fe...@gmail.com on 13 Mar 2014 at 2:19