DSSAT Batch should keep submitted order. about translator-dssat HOT 7 CLOSED

Does it only happen in multiple tread mode? I have checked the code for generating batch file and currently it is accept the array of all experiment data and loop it to write command line one by one. Therefore I think it is match with the logic above. I also tried multiple experiment output together to see how the batch file would be generated, and as a result I didn't find the order got shuffled.

from translator-dssat.

It is with the thread mode. Do you have your own thread implementation inside your translator?

from translator-dssat.

I checked my code that I created a class called DssatThreadOutput to wait for your call. I also find that in the thread output, I passed experiment data one by one to the controller output. Therefore, it should create a bunch of zip package with only one experiment inside. As a result, I want to confirm if you have used this class in your side. If so, do you have any code to combine those zips into one zip with all experiment files?
In addition, when the tread mode will be used? By using QuadUI?

from translator-dssat.

• The front-end tools (QuadUI and API) are calling DssatOutputController.writeFile().
• The translators should be responsible for packaging all the files into whatever format is necessary for them.
• Threaded-mode should be used by all translators eventually, for speed.

Here is some pseudo-code for the way I see it working.

ArrayList<String> experimentNames = new ArrayList<String>();
// Since we are receiving packed files, unpack the files.
ArrayList<Map<String, Object>> flat = MapUtil.flatPack(experiementsMap);
for (Map<String, Object> experiment : flat) {
   // Extract the name of the experiment
   experimentNames.add(MapUtil.getValueOr(experiment, "exname", "");
  // Submit this to a thread processor for work
  ...
}

// Use experimentNames to export DSSATBatch.

from translator-dssat.

If front-end tool always call DssatOutputController.writeFile(), then it can be considered as there is no thread implementation inside the DSSAT translator.

from translator-dssat.

Okay. I'll look more into it. I don't see any scrambled processes unless it's threaded.

from translator-dssat.

The error is on the input side. I found the issue and am addressing it on that side.

from translator-dssat.