alternate sources for parameters (named_location/filename_location)

View: New views
2 Messages — Rating Filter:   Alert me  

alternate sources for parameters (named_location/filename_location)

by Patrick Ohly-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I want to parse two different input files, one where a parameter is
determined by lines inside the file (named_location), the other where it
is only available as part of the file name (filename_location).

What I find with --debug is that when it comes to storing the values of
a tabular_location, both the information from the filename and the line
seems to be available, but neither of them is used in the final dataset.
The debug output is something like this:

#* storing dataset
#* dataset is  None None
#* dataset is  ['peer'] {'peer': '<from file content>'}
...
#* dataset is  ['peer'] {'peer': '<from file name>'}
#* dataset is  [...] {...}
Dataset 0 in run 3
{..., 'peer': None, ... }

Is this the expected behavior? I'll go back to writing two input
specifications to avoid the situation, but I think a conflict resolution
where the "more recent" named_location overrides the "static/default"
filename_location parameter value would be useful. I might miss use
cases where that is not the case, though.

--
Best Regards

Patrick Ohly
Senior Software Engineer

Intel GmbH
Software & Solutions Group                
Hermuelheimer Strasse 8a                  Phone: +49-2232-2090-30
50321 Bruehl                              Fax: +49-2232-2090-29
Germany

Intel GmbH, Dornacher Strasse 1, 85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456
Ust.- IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...


Re: alternate sources for parameters (named_location/filename_location)

by Joachim Worringen-4 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Patrick Ohly schrieb:

> Hello,
>
> I want to parse two different input files, one where a parameter is
> determined by lines inside the file (named_location), the other where it
> is only available as part of the file name (filename_location).
>
> What I find with --debug is that when it comes to storing the values of
> a tabular_location, both the information from the filename and the line
> seems to be available, but neither of them is used in the final dataset.
> The debug output is something like this:
>
> #* storing dataset
> #* dataset is  None None
> #* dataset is  ['peer'] {'peer': '<from file content>'}
> ...
> #* dataset is  ['peer'] {'peer': '<from file name>'}
> #* dataset is  [...] {...}
> Dataset 0 in run 3
> {..., 'peer': None, ... }
>
> Is this the expected behavior? I'll go back to writing two input
> specifications to avoid the situation, but I think a conflict resolution
> where the "more recent" named_location overrides the "static/default"
> filename_location parameter value would be useful. I might miss use
> cases where that is not the case, though.

Can you write a small testcase for this (experiment and input
description, input files)? This would make it much easier to analyze this.

  Joachim

--
Joachim Worringen, Software Architect, Dolphin Interconnect Solutions
phone ++49/(0)228/324 08 17 - http://www.dolphinics.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...