Pointspec deleted

[srothmei]

Hey,

we're experiencing some weird behaviour using the JWSreqests-Tool:
Within our testdata/workspace, we got several multidocuments including outlierdata.
After we apply the JWSreq tool to the workspace, the corresponding entry within the XML-tree of the SAProcessing-XMLfile is deleted, thus the outlier-detection isn't performed anymore.

For example, this is the state of a single MultiDoc/sa-item before using JWSreq (i omitted some lines of XML for the sake of readability here):

    <item name="sa5">
        <subset>
            <item name="name">
            <item name="ts">
            <item name="domainspec">
            <item name="pointspec">
            <item name="estimationspec">
            <item name="quality">
            <item name="metadata">
        </subset>
    </item>

And now after JWSreq:

    <item name="sa5">
        <subset>
            <item name="name">
            <item name="ts">
            <item name="domainspec">
            <item name="estimationspec">
            <item name="metadata">
        </subset>
    </item>

Note that the elements <item name="pointspec"> and <item name="quality"> are both gone.

From my understanding, it seems strange that the tool is manipulating the files at all. Shouldn't it be supposed solely to create the corresponding x13req-files?

[palatej]

Hi Simon,

I don't believe that it is an issue.
When you use the WSRequests tool you actually do two things:

• You refresh the current series and you update the specification using the specified policy (by default, you just recompute the various parameters)
• You generate the corresponding xml for the WEB service.

The first step means that the current point specs (and also the quality diagnostics) are no longer valid and should be removed or updated. As the actual computation is delegated to the WEB service, they are in our case simply removed.

If you want to re-estimate more things, you must use the "policy" tag in the spec file. See the doc on the Cruncher for more detail.

If we don't want to modify the current files, we have to modify the current implementation or - of course - you use a copy.

[srothmei]

Hi Jean,

thanks for the reply.

So if i'm getting this right, it means that once we insert a valid pointspec it will still be present in the xml file generated for the Web-Service. Thus we have to check why the spec isnt valid for our data.

Since it think our meth. dept. wants to preserve the original files as far as possible, we could turn of the file-manipulation directly via the parameters.