Ruta UIMAFIT component declaration with configuration parameters
Hello, I can't seem to find how to define additional configuration parameters for UIMAFIT components in Ruta scripts, something along the lines of: UIMAFIT org.apache.uima.ruta.engine.XMIWriter, 'Output', '/path/to/xmi.xml'; (How) is this possible? Thanks, Renaud
Re: UIMA pipeline output persistence and multiple layer web based visualisation tools? Suggestions?
Hi James, taking Apache UIMA hat off, putting UKP Lab hat on I'm working on the WebAnno (and DKPro Core) project. Thanks for checking it out and providing feedback! On 16.11.2014, at 13:08, James Kitching jameskitch...@hemseye.org wrote: I had hoped that I could use webanno for this task however webanno does not allow the direct import of UIMA components or UIMA output. WebAnno [1] is an annotation tool. It's scope is not the building or running of pipelines. WebAnno can quite immediately consume XMIs created with the DKPro Core [2] collection of UIMA components, since the built-in annotation types of WebAnno are modelled after the DKPro Core types. Actually, all import/export filters in WebAnno are UIMA components from DKPro Core. WebAnno is not meant to be a universal XMI/CAS editor. It is meant to be a user-friendly annotation tool. However, we internally use the UIMA CAS to represent annotations. To visualizes UIMA annotations in WebAnno, they need to be mapped to WebAnnos (cf. brat's) interaction paradigms. To this end, WebAnno supports three specific type-system design patterns (aka layer types): span, relation, and chain. A span is basically a UIMA Annotation. A relation is an annotation with two features pointing to a span type. A chain is basically a variation of a linked list. Additional primitive features are also supported. If you want to use WebAnno with existing UIMA data, you can try this: - define custom annotation layers in WebAnno that closely resemble the data you wish to interface with - export the layer definition as JSON - edit the JSON file and change the type names webanno.custom.XXX into whatever these types are called in your existing UIMA type sytem - create a new project - import the modified JSON layer configuration For basic type system designs, this should work ok. Cheers, -- Richard [1] https://code.google.com/p/webanno/ [2] https://code.google.com/p/dkpro-core-asl/
Re: UIMA pipeline output persistence and multiple layer web based visualisation tools? Suggestions?
Hi Richard, Thanks very much for your replies (UIMA and webanno groups). I have updated my research blog with your response and will hopefully soon get to a point where I can follow the advice you have given. Regards James Kitching On 16/11/2014 13:08, Richard Eckart de Castilho wrote: Hi James, taking Apache UIMA hat off, putting UKP Lab hat on I'm working on the WebAnno (and DKPro Core) project. Thanks for checking it out and providing feedback! On 16.11.2014, at 13:08, James Kitching jameskitch...@hemseye.org wrote: I had hoped that I could use webanno for this task however webanno does not allow the direct import of UIMA components or UIMA output. WebAnno [1] is an annotation tool. It's scope is not the building or running of pipelines. WebAnno can quite immediately consume XMIs created with the DKPro Core [2] collection of UIMA components, since the built-in annotation types of WebAnno are modelled after the DKPro Core types. Actually, all import/export filters in WebAnno are UIMA components from DKPro Core. WebAnno is not meant to be a universal XMI/CAS editor. It is meant to be a user-friendly annotation tool. However, we internally use the UIMA CAS to represent annotations. To visualizes UIMA annotations in WebAnno, they need to be mapped to WebAnnos (cf. brat's) interaction paradigms. To this end, WebAnno supports three specific type-system design patterns (aka layer types): span, relation, and chain. A span is basically a UIMA Annotation. A relation is an annotation with two features pointing to a span type. A chain is basically a variation of a linked list. Additional primitive features are also supported. If you want to use WebAnno with existing UIMA data, you can try this: - define custom annotation layers in WebAnno that closely resemble the data you wish to interface with - export the layer definition as JSON - edit the JSON file and change the type names webanno.custom.XXX into whatever these types are called in your existing UIMA type sytem - create a new project - import the modified JSON layer configuration For basic type system designs, this should work ok. Cheers, -- Richard [1] https://code.google.com/p/webanno/ [2] https://code.google.com/p/dkpro-core-asl/
DUCC 1.1.0- How to Run two DUCC version on same machines with different user
Hi, I want to run two DUCC version i.e. 1.0.0 and 1.1.0 on same machines with different user. Can this be possible? Thanks in advanced. Reshu.
Re: DUCC-1.1.0: Machines are going down very frequently
Dear Lou,
I am using default configuration:
ducc.agent.node.metrics.publish.rate=3
ducc.rm.node.stability = 5
Reshu.
Signature On 11/12/2014 05:03 PM, Lou DeGenaro wrote:
What do you have defined in your ducc.properties for
ducc.rm.node.stability and ducc.agent.node.metrics.publish.rate? The
Web Server considers a node down according to the following
calculation:
private long getAgentMillisMIA() {
String location = getAgentMillisMIA;
long secondsMIA = DOWN_AFTER_SECONDS*SECONDS_PER_MILLI;
Properties properties = DuccWebProperties.get();
String s_tolerance = properties.getProperty(ducc.rm.node.stability);
String s_rate =
properties.getProperty(ducc.agent.node.metrics.publish.rate);
try {
long tolerance = Long.parseLong(s_tolerance.trim());
long rate = Long.parseLong(s_rate.trim());
secondsMIA = (tolerance * rate) / 1000;
}
catch(Throwable t) {
logger.warn(location, jobid, t);
}
return secondsMIA;
}
The default is 65 seconds. Note that the Web Server has no effect on
actual operations in this case. If is just a reporter of information.
Lou.
On Wed, Nov 12, 2014 at 12:45 AM, reshu.agarwal
reshu.agar...@orkash.com wrote:
Hi,
When I was trying DUCC-1.1.0 on multi machine, I have faced an up-down
status problem in machines. I have configured two machines and these
machines are going down one by one. This makes the DUCC Services disable and
Jobs to be initialize again and again.
DUCC 1.0.0 was working fine on same machines.
How can I fix this problem? I have also compared ducc.properties file for
both versions. Both are using same configuration to check heartbeats.
Re-Initialization of Jobs are increasing the processing time. Can I change
or re-configure this process?
Services are getting disabled automatically and showing excessive
Initialization error status on mark over on disabled status but logs are not
showing any error.
I have to use DUCC 1.0.0 instead of DUCC 1.1.0.
Thanks in Advance.
--
Signature *Reshu Agarwal*
