-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev/repair develop #270
Dev/repair develop #270
Conversation
@@ -136,7 +139,8 @@ def inference(self, img: torch.tensor, interpolate: bool = False): | |||
pad = int((W - H) / 2) | |||
features = F.interpolate(features, new_size, mode="bilinear", align_corners=True) | |||
features = F.pad(features, pad=[pad, pad, 0, 0]) | |||
|
|||
# Optionally turn on image feature smoothing | |||
# features = filter2d(features, self.mean_kernel, "replicate") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did smoothening feature help in some cases?
std = 400 | ||
mean = 550 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This we should set in the LossAnomalyParams. These parameters were found with a test dataset per environment. We should update this during online learning with a rolling window from the traversed features.
@@ -26,13 +26,10 @@ segmentation_type: "random" | |||
feature_type: "dino" | |||
dino_patch_size: 16 # DINO only | |||
confidence_std_factor: 4.0 | |||
scale_traversability: True | |||
scale_traversability: False # This parameter needs to be false when using the anomaly detection model |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add logic to set to false automatically
@@ -273,5 +360,16 @@ def load_model(self): | |||
if __name__ == "__main__": | |||
node_name = "wvn_feature_extractor_node" | |||
rospy.init_node(node_name) | |||
|
|||
if True: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hacky :)
|
…visual_navigation into dev/repair_develop
Changes from deployment on robot
…isual_navigation into dev/repair_develop
…isual_navigation into dev/repair_develop
Keeping track of changes:
Improved the logging of the feature_extraction node, which makes it easy to keep track if the node is up and running.
The pipeline is alive:
Slic features also works nicely: