[Pellet-users] Pellet 1.5 stalls Protege

[Bijan Parsia]

On Sep 21, 2007, at 5:14 AM, Trina Myers wrote:

> Hi Bijan,
>
> Thanks for your quick response. I am using the DIG server mainly  
> because I
> am also implementing rules (SWRL) which won't be available in  
> Protégé 4 for
> some time.

Erhm...I'd be a tad surprised if DIG supported rules...I guess it'll  
pass the encoding of the rules over and probably Pellet would  
recognize them.

> I have tested Pellet in Protégé 4 and it just hangs (at 2%),

Ok, that's weird.

> I tried the
> FacT++ implementation in Protégé 4 and it went OK.
> I tested Top Braid Composer and the internal Pellet worked fine,

And that.

> but when
> accessing the Dig version through 8081 it locks up as well (60% cpu).

And this happens only on the one machine? That's *really* weird.

> I ran Pellet directly from the command line and although there was no
> excessive CPU usage, it didn't seem to classify the ontology (am  
> not fully
> familiar with command line usage of the Reasoners), I have attached  
> the
> output...

C:\Program Files\pellet-1.5.0>java -Xss4m -Xms30m -Xmx200m -jar lib 
\pellet.jar -
s off -c TREE -cout test.txt -if GBRclasses.owl
Input file: file:/C:/Program%20Files/pellet-1.5.0/GBRclasses.owl
org.mindswap.pellet.exceptions.InternalReasonerException: This  
interval does not
have 1428362263 values

Looks like there's a problem with some datatype assertions (do the  
other machines *return at all*?) Ooh, I hope Pellet isn't trying all  
those values in all combinations :)

What's the ontology?

And you say this happens only on one machine? What does the Pellet  
command line say there?

Cheers,
BIjan.