Degree Filter Not Filtering as Subfilter in Tookit

Bug #878962 reported by Elijah Meeks
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gephi
Confirmed
High
Mathieu Bastian

Bug Description

I've nested a Partition filter in a Degree filter and it doesn't filter out the Degree 0 values. It does seem to work if the minimum degree value is set to 2. The attached gexf and main script are what I'm using.

Revision history for this message
Elijah Meeks (emeeks-stanford) wrote :
Revision history for this message
Elijah Meeks (emeeks-stanford) wrote :

Here's the graph I'm trying to filter

Revision history for this message
Mathieu Bastian (mathieu.bastian) wrote :

I didn't test with your graph yet but I think this bug happens because of some boundary update code. The problem appears when the range is out of the boundary. In Gephi we always show you the range you can filter (with a min and a max) so you can't set up an incorrect filter. For instance if the ma degree is 10 and the min is 3 you can't create a filter [3, 200]. If you do, the system will automatically prune 200 to the limit 10. That is what is happening here I think. The range is changed and therefore the filter doesn't work.

I fixed something in the Range class and did some tests on a random graph. Can you please pull the trunk, build the new toolkit and test?

In addition I fixed another bug so you don't have to call init() on your filters anymore. That should be done by the system, but it was throwing an exception without.

Moreover, you can now execute a layout with N iterations directly from the layout controller:
LayoutController layoutController = Lookup.getDefault().lookup(LayoutController.class);
layoutController.setLayout(layout);
layoutController.executeLayout(200);

Changed in gephi:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Mathieu Bastian (mathieu.bastian)
Revision history for this message
Elijah Meeks (emeeks-stanford) wrote :

I pulled the latest trunk and rebuilt the Toolkit and I'm still having an issue--I think your fix took care of the inconsistency I was seeing with differing range values put in. However, I still end up with the filter being ignored but now it is consistently only happening if the MIN value is set to 1. It seems that once the MIN value goes above 1, that it filters as expected, but when set at 1, it's ignored (the partition filter is always applied, regardless).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.