Re: [recommenders-dev] Stacktrace parser/detector

[Marcel Bruch <marcel.bruch@xxxxxxxxx>]

Just to extend Johannes' mail.

We conducted several evaluations on how well duplicate detection with various search algorithms works on the Eclipse Bugzilla dataset. We evaluated these search engines using various Apache Lucene configurations (own word splitter, different scoring etc.) as well as several classifiers.

The UI screenshots you see in the blog-post is a student prototype created during a hands-on. We have set up a preliminary server-side based on JAX-RS (Oracle Jersey) + Apache CouchDB + Apache Lucene to store and search for similar stacktraces. Metadata to represent stacktraces is also their - but is slightly different to your representation in Scala. BTW: its all written in Java.

We also have a preliminary version of a crawler for various forums to identify stacktraces in forum posts etc. This is thought to create an inital dataset to see how well this engine actually works.

Just to make a quick shot:

We need a clear vision of how the UI should look like and how users will/should use the tool. We have though of a web ui + an Eclipse ui. How about starting to design a Web UI that gives a clear intuition how people could use the web interface? I think this UI could be quite simple w/o advanced editing functionality etc.

Paulo, what's your though? Do you want to come up with a draft for a web ui? Afterwards, we should think about how we fill the data into a server side. And writing a paper would always be interesting (thats actually one of our goals too. So we could benefit both from joint work). I've several evaluation ideas already in my mind...


Best,
Marcel

On 31.05.2011, at 09:28, Johannes Lerch wrote:

> Hi Paulo Sérgio,
> 
> can you send me the papers you found?
> 
> We have some initial thoughts about what we want to do in the first
> steps, but i think these ideas are not documented yet. First step is
> to crawl multiple platforms like bugzilla for stacktraces and save
> those with a link to it's source. If we have some initial dataset we
> will create a search index and provide a platform on which anyone can
> search for a stacktrace. We should be able to show links to the
> previously crawled resources in the web which match the searched
> stacktrace.
> A later step could be, that we allow discussions and help topics on
> that search platform itself.
> 
> Can you outline what is implemented in your project already?
> 
> Regards,
> Johannes
> 
> 
> 2011/5/31 Paulo Sérgio Medeiros <pasemes@xxxxxxxxx>:
>> Hi all,
>> 
>> I'm here coming from my first contact with Marcel in his post at code
>> recommender's blog
>> (http://code-recommenders.blogspot.com/2011/05/oh-stacktrace-my-stacktrace.html).
>> 
>> I have already stated in my comment there that I'm trying to build
>> (https://github.com/pasemes/buggenome - very initial stage, look at the
>> devmatcher branch for more recent code base) something very similar to the
>> ideas exposed in the post. So, the intent of this thread is to offer myself
>> to contribute to the initiative.
>> 
>> First, I would like to know if you have already elaborated something like an
>> initial list of functionalities or initial sketch of the concepts and/or
>> architecture.
>> 
>> I don't have much documentation on what I have done. But to organize my
>> initial ideas I have searched for papers (I'm a PhD student :-) to see if
>> anyone implemented something similar. I found some papers the describe some
>> heuristics to search for similar stacks. However, reading Marcel's post I
>> realized that I've missed that there are implementations of similar stack
>> detectors in Jira and Bugzilla :-(. Anyway, I can send the papers if you are
>> interested. Another thing that I've is a mindmap with some of my
>> understanding of the readings. It's in Portuguese, my mother tongue, but I
>> can translate that easily and send to you too.
>> 
>> So, that's it for now. I just want to hear what steps to follow. I took a
>> look at the project wiki and saw that you have lots of docs for
>> contributors, but I'll wait for your pointers on how to setup the source
>> control tools and stuff like that if that's the case.
>> 
>> Best regards,
>> Paulo Sérgio.
>> _______________________________________________
>> recommenders-dev mailing list
>> recommenders-dev@xxxxxxxxxxx
>> http://dev.eclipse.org/mailman/listinfo/recommenders-dev
>> 
>> 
> _______________________________________________
> recommenders-dev mailing list
> recommenders-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/recommenders-dev