Difference between revisions of "User:Zolta"
m (→Protege 4 related issues I'm interested in) |
(→Title the Scroll Lock saved me.) |
||
| Line 20: | Line 20: | ||
Okay here's the short story: | Okay here's the short story: | ||
| − | ==== | + | ====My Story : The Scroll Lock saved my day.==== |
| − | Today I'm working on my final school project | + | Today I'm working on my final school project '':-) Could you help me? :-) '' |
| − | I decided to use owl quite a long time ago. | + | |
| + | I decided to use owl quite a long time ago. Now the time has come. Now I'm clicking and typing and --Wow-- I'm designing an ontology. | ||
| + | |||
| + | But the above message made me sad and it did annoy me. | ||
| + | |||
| + | these things happened | ||
| + | |||
| + | It was because my console window which held Protege console messages had an unlimited buffer. The unlimited buffer of the console window and the experienced behaviour by the Protege 4.0 build 113 (sometimes it starts to throw a huge amount of '''strange exception java.io.IOException: Bad file descriptor''' flooded my temp directory /tmp which is luckily on a separate partition which also causes high load of CPU of course | ||
| + | then suddenly I zoomed on the Scroll Lock key on the keyboard and eagerly pressed it. This Action solved my problem and this strange exception does'nt annoy me any more. | ||
| + | (To be honest I also cleared the option ''Write temporary files when saving'' at Files>Preferences>Save (tab)) | ||
| + | But I'd like to understand why it is present and I'd like to contribute to get rid of it. | ||
| + | |||
| + | I use 2 owl files ( Class count 34; Object property count Individual count 11 SubClass Axioms count 42) but I think it doesn't matter. | ||
| + | Could you help me to understand the problem? | ||
| + | Could you guide me please how could I contribute to get rid of this problem? | ||
Revision as of 14:35, August 17, 2009
Greetings to all.
Contents
Personal details
- I'm a protege 4 user quite a newbie as of build 112 is the current one
- In the present I use protege 4.0 Build 113 --Zolta 20:51, August 17, 2009 (UTC)
- my environment is Linux (Debian Lenny) 2.6.22-3-k7 #1 SMP (sometimes with KDE)
- my JVM is 1.6.0_16
- my top level uri is [1]
- my name 's Zoltan Baráti
I'd like to contribute.
Can I help you?
...
strange exception java.io.IOException: Bad file descriptor
strange exception java.io.IOException: Bad file descriptor message from the console output annoys me. --Zolta 20:57, August 17, 2009 (UTC)
Okay here's the short story:
My Story : The Scroll Lock saved my day.
Today I'm working on my final school project :-) Could you help me? :-)
I decided to use owl quite a long time ago. Now the time has come. Now I'm clicking and typing and --Wow-- I'm designing an ontology.
But the above message made me sad and it did annoy me.
these things happened
It was because my console window which held Protege console messages had an unlimited buffer. The unlimited buffer of the console window and the experienced behaviour by the Protege 4.0 build 113 (sometimes it starts to throw a huge amount of strange exception java.io.IOException: Bad file descriptor flooded my temp directory /tmp which is luckily on a separate partition which also causes high load of CPU of course then suddenly I zoomed on the Scroll Lock key on the keyboard and eagerly pressed it. This Action solved my problem and this strange exception does'nt annoy me any more. (To be honest I also cleared the option Write temporary files when saving at Files>Preferences>Save (tab)) But I'd like to understand why it is present and I'd like to contribute to get rid of it.
I use 2 owl files ( Class count 34; Object property count Individual count 11 SubClass Axioms count 42) but I think it doesn't matter. Could you help me to understand the problem? Could you guide me please how could I contribute to get rid of this problem?
