It's around 9000 frames with mostly just bounding boxes. There are a
significant number(~15) of other attributes that are either booleans
or numbers, but I don't think they'd affect it too greatly as they're
mostly primitive and usually simple data types.
I think at the time this started happening I had about 6 targets in
the file.
I did increase the heap size further to 2 gb, and the problem wasn't
really noticeable anymore, so I think that confirms it was a problem
with the heap size.
I did start doing individual files for annotating and combining them
with the converter class, which seems to work better now that I have
it working. May I suggest that you either increase your documentation
on the converter class (as it's very useful for keeping the speed up
as well as having less clutter) or put in some sort of functionality
into the Viper GUI to combine files. It would be great if I could
select the two files I want to combine and specify an output file.
Also, in the interest of saving space without making another thread. I
noticed that the converter class writes it's XML all in a single line.
It would be nice if it combined annotations so they were in the same
visual format Viper generates it's XML. This is, of course, very minor
compared to having the converter functionality being a little more
accessible.
On Aug 16, 9:07 pm, David Mihalcik <kraka...@gmail.com> wrote:
> Hmm... Not sure what the problem could be. About how many frames &
> with what type of data are you annotating? Say, 40k frames of
> polygons, or something complicated, or something simpler?
> On Aug 14, 11:59 am, way2lazy2care <roon...@uwstout.edu> wrote:
> > I've been annotating in Viper for a few days, and I just came across a
> > crippling performance issue. I think it's related to the issue here:
> >http://groups.google.com/group/viper-toolkit/browse_frm/thread/5eb995...
> > I was annotating an ~5 minute long file, and had 4 things being
> > annotated on and off throughout the clip. By the time I was nearly
> > finished with the fourth, I would be able to use Viper for maybe 5
> > minutes before performance would drop to the point where Viper would
> > nearly completely freeze. I figured this was the heap filling up.
> > I increased my maximum heap size to 1gb (which should be fine on this
> > computer) and made a new file to continue annotating to merge with the
> > other later.
> > I started annotating with the new Viper file, and after 5 minutes
> > again the program pretty much freezes. It uses ~30% of my CPU (it uses
> > ~5% when first opened and stays about the same if I just play the
> > movie) even when there is nothing happening in the program.
> > I have no idea what the problem could be now, but I can't really do
> > much with Viper till I know what could be causing the problem.
|
