|Message: Re: Proble with OpenScientist v16r0||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Hello Then, after an "offline" session, the problem comes from the fact that in OSC-15 I had put the logic, that if someone asks for the "hbook" format and that the HBOOK/ZEBRA driver of OSC was not here, then I produced an AIDA XML file format (obviously by issuing some warnings). But it appeared at usage (with other users here at LAL) that this in fact was awfully misleading since files are produced in batch and that the warnings finished to be not noticed in the flow of G4 outputs. And then people expect a .hbook and finish to have a .aida ! (And no way to trace things in the program, since a valid AIDA::ITree was anyway created). And then I have removed this logic in OSC-16. Now if someone ask for a given storage type and that the installed version has not the driver, then no file is produced. (Obviously some warnings are issued and the factory returns 0 at creation of the AIDA::ITree and then the user program can detect that something is wrong). Then in your case, in the code, it was requestd "hbook", but your OSC-15 produced a .aida that you were able to open with jas3. But since the osc_batch 16 kits have all the hbook drivers, now you have a true .hbook file. And it seems that your jas3 does not understand them. (Huum, I though that jas3 was able to open a .hbook file, but you have perhaps not some hbook reader plugin : you have to see with jas people here). Then, a way out, if wanting to use jas3 is to explicitly ask for "aida" or "xml" file production in your job. (Or arrange that your jas3 be able to read .hbook file). (You can learn PAW too...) (or try to use OSC/opaw). Guy
|Inline Depth:||Outline Depth:||Add message:|