#2706 closed help (fixed)

avoid duplexing data in MASS

Reported by: ggxmy Owned by: ros
Component: Archiving Keywords:
Cc: Platform: Monsoon2
UM Version: 11.0


Hi. I got an email from a person at Met Office telling to avoid duplexing the data in MASS. I felt this was a bit strange because all I did was to copy the release job (u-bb202) and ran it for myself.

Anyway I tried to follow ticket #2376 to modify the suite, but quite naturally what I have here with my vn11.0 suite seems to be a bit different from what is written in #2376 which is about vn10.6.1. Could I have an instruction for how I should modify my vn11.0 suite to avoid data duplexing?

To be specific, in the first step what should I do in rose edit - Metadata - Upgrade… And then what should I do in rose edit - fcm_make_pp ? Or should I do something different for this version?

Many thanks.

Change History (2)

comment:1 Changed 19 months ago by ros

  • Owner changed from um_support to ros
  • Status changed from new to accepted

Hi Masaru,

I'm not sure exactly what information the Met Office are working off, but it's possible it's just because you've had some suite in the recent past with duplexing on. Anyway assuming you are talking about suite u-bd780 then it is already set to non-duplexing.

For future reference the duplexing switch is in panel postproc → post processing - common settings → moose archiving and make sure the option non_duplexed_set is set to true.


comment:2 Changed 19 months ago by ggxmy

  • Resolution set to fixed
  • Status changed from accepted to closed

HI Ros.,

Thank you for your help. As you say it will be great for future reference, but it wasn't actually a problem. They say;

The routine simplex/duplex check email gets sent out to everybody who has created sets so they can check that they've set them up correctly.

I should have simply asked them what was the problem and how I could fix it. I asked here because they didn't appear to be UM experts.


Note: See TracTickets for help on using tickets.