Re: Saving inferred ontology

Timothy Redmond <[email protected]> Fri, 27 Sep 2013 14:29:17 -0700
Newsgroups gmane.comp.misc.ontology.protege.general
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--===============1968437976357639432==
Content-Type: multipart/alternative;
 boundary="------------090308010109020203010108"

This is a multi-part message in MIME format.
--------------090308010109020203010108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 09/26/2013 04:49 PM, Andr=E9 Luiz Tietb=F6hl Ramos wrote:
> Hello everyone,
>
> I have a relatively large ontology that takes a long time to be=20
> inferred.  It is under development right now. In addition, I'd like to=20
> save the final inferred versions directly. Is it possible?

Protege 4 will let you export inferred axioms into an ontology.  Use=20
File->Export Inferred Axioms as ontology.

>
> BTW, the best way to speed up the inference process to add more memory?

As far as I know, adding memory won't help speed things up for most=20
reasoners.  I think that adding memory will only help, and in this case=20
it will help quite a bit, if you are right at the edge of running out of=20
memory for your java virtual machine.  What happens in this case is that=20
sometimes java will run extremely slowly because it is spending=20
tremendous amounts of time doing garbage collection.  But if java has=20
sufficient memory, adding more won't help.

Unfortunately I don't know of a general way of telling if the java=20
process lost in garbage collection.  If you use the jdk version of java,=20
you can connect to the java program with jvisualvm and use this to=20
monitor the amount of garbage collection.

One other distinction is whether you are finding inference slow in that=20
period when it is initializing or if Protege 4 just runs too slowly=20
after the reasoner has initialized and you are moving about the=20
interface.  If the initialization phase is too slow then your main=20
viable option is to try other reasoners.

If the Protege 4 user interface is too slow after the reasoner has=20
initialized, then this is happening because certain inferences that=20
Protege is displaying are taking too long to calculate.  In this case,=20
you can control the inferences that Protege displays by configuring the=20
options in the Reasoner->Configure dialog.  There is a youtube video=20
that tells how to do this:

                          https://www.youtube.com/watch?v=3DqnC6x4iZFyw


This can also be used to control what the reasoner does when it=20
initializes but this is not usually recommended because it may result in=20
a slow-down of Protege after the reasoner has initialized because it has=20
not cached a sufficient set of inferences.


-Timothy.


>
> Thanks,
>
> --=20
> Andre Luiz Tietbohl Ramos
> http://www.feng.pucrs.br/~andreltr <http://www.feng.pucrs.br/%7Eandrelt=
r>
>
>
>
>
> _______________________________________________
> protege-discussion mailing list
> [email protected]
> https://mailman.stanford.edu/mailman/listinfo/protege-discussion
>
> Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.htm=
l#01a.03


--------------090308010109020203010108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 09/26/2013 04:49 PM, Andr&eacute; Luiz
      Tietb&ouml;hl Ramos wrote:<br>
    </div>
    <blockquote cite="mid:1380239392.4568.5.camel@Sigmatech" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <meta name="GENERATOR" content="GtkHTML/4.6.4">
      Hello everyone,<br>
      <br>
      I have a relatively large ontology that takes a long time to be
      inferred.&nbsp; It is under development right now. In addition, I'd
      like to save the final inferred versions directly. Is it possible?
      <br>
    </blockquote>
    <br>
    Protege 4 will let you export inferred axioms into an ontology.&nbsp; Use
    File-&gt;Export Inferred Axioms as ontology.<br>
    <br>
    <blockquote cite="mid:1380239392.4568.5.camel@Sigmatech" type="cite">
      <br>
      BTW, the best way to speed up the inference process to add more
      memory?<br>
    </blockquote>
    <br>
    As far as I know, adding memory won't help speed things up for most
    reasoners.&nbsp; I think that adding memory will only help, and in this
    case it will help quite a bit, if you are right at the edge of
    running out of memory for your java virtual machine.&nbsp; What happens
    in this case is that sometimes java will run extremely slowly
    because it is spending tremendous amounts of time doing garbage
    collection.&nbsp; But if java has sufficient memory, adding more won't
    help.&nbsp; <br>
    <br>
    Unfortunately I don't know of a general way of telling if the java
    process lost in garbage collection.&nbsp; If you use the jdk version of
    java, you can connect to the java program with jvisualvm and use
    this to monitor the amount of garbage collection.<br>
    <br>
    One other distinction is whether you are finding inference slow in
    that period when it is initializing or if Protege 4 just runs too
    slowly after the reasoner has initialized and you are moving about
    the interface.&nbsp; If the initialization phase is too slow then your
    main viable option is to try other reasoners.<br>
    <br>
    If the Protege 4 user interface is too slow after the reasoner has
    initialized, then this is happening because certain inferences that
    Protege is displaying are taking too long to calculate.&nbsp; In this
    case, you can control the inferences that Protege displays by
    configuring the options in the Reasoner-&gt;Configure dialog.&nbsp; There
    is a youtube video that tells how to do this:<br>
    <br>
    <pre>                         <a class="moz-txt-link-freetext" href="https://www.youtube.com/watch?v=qnC6x4iZFyw">https://www.youtube.com/watch?v=qnC6x4iZFyw</a>
</pre>
    <br>
    This can also be used to control what the reasoner does when it
    initializes but this is not usually recommended because it may
    result in a slow-down of Protege after the reasoner has initialized
    because it has not cached a sufficient set of inferences.<br>
    <br>
    <br>
    -Timothy.<br>
    <br>
    <br>
    <blockquote cite="mid:1380239392.4568.5.camel@Sigmatech" type="cite">
      <br>
      Thanks,<br>
      <br>
      <table cellpadding="0" cellspacing="0" width="100%">
        <tbody>
          <tr>
            <td>
              -- <br>
              Andre Luiz Tietbohl Ramos<br>
              <a moz-do-not-send="true"
                href="http://www.feng.pucrs.br/%7Eandreltr">http://www.feng.pucrs.br/~andreltr</a>&nbsp;<br>
              <br>
              <br>
            </td>
          </tr>
        </tbody>
      </table>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
protege-discussion mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a>
<a class="moz-txt-link-freetext" href="https://mailman.stanford.edu/mailman/listinfo/protege-discussion">https://mailman.stanford.edu/mailman/listinfo/protege-discussion</a>

Instructions for unsubscribing: <a class="moz-txt-link-freetext" href="http://protege.stanford.edu/doc/faq.html#01a.03">http://protege.stanford.edu/doc/faq.html#01a.03</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------090308010109020203010108--

--===============1968437976357639432==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
protege-discussion mailing list
[email protected]
https://mailman.stanford.edu/mailman/listinfo/protege-discussion

Instructions for unsubscribing: http://protege.stanford.edu/doc/faq.html#01a.03

--===============1968437976357639432==--