search

fritzing / fritzing-app

Fritzing desktop application
http://fritzing.org
Other
4.01k stars 828 forks source link

Autorute fault #2933

Closed davidperrenoud closed 4 years ago

davidperrenoud commented 10 years ago

From ramon...@gmail.com on March 18, 2014 09:50:19

What steps will reproduce the problem? 1.If you autorute the file "Tarjeta TEG sin rutear" some wires dissapear. I copy files before and after("Tarjeta TEG ruteada"), in the SMDs 20pins some wires are missed after autorute.

  1. I hope do not loose connectios when autorute. 3.fritzing.0.8.7b.pc Attach your sketch file and/or custom part files to the bug report. What is the expected output? What do you see instead? What version of Fritzing are you using? On what operating system? Please, let me know any way to go on, any advice will be great to finish, very close to do it.

Best regards,

Ramón Villanova. Please provide any additional information below.

Attachment: Tarjeta TEG sin rutear.fzz Tarjeta TEG ruteada.fzz

Original issue: http://code.google.com/p/fritzing/issues/detail?id=2935

davidperrenoud commented 10 years ago

From andre.knoerig@gmail.com on March 22, 2014 10:38:35

Status: Accepted
Labels: -Priority-Medium Priority-High Component-Autorouter

davidperrenoud commented 10 years ago

From andre.knoerig@gmail.com on April 23, 2014 07:50:19

probably related to issue 2921

davidperrenoud commented 10 years ago

From andre.knoerig@gmail.com on April 23, 2014 07:52:36

Status: Duplicate
Mergedinto: 2921

davidperrenoud commented 10 years ago

From irasc...@gmail.com on May 07, 2014 00:38:30

It is not clear this is a duplicate of 2921--though it might be--so I am restoring its independent status.

This is a case in which wiring has been done in only pcb view. When then attempting to autoroute in pcb view, the autorouter is unable to complete at 100 tries, so some of the connections must by definition be lost (since a success in this case would mean rerouting what is already there).

Some choices for this particular file are: -- do the wiring in another view, so that you can see ratsnests if the autorouter doesn't complete -- bump up the number of tries given to the autorouter, in the hope that it will succeed (note, it still doesn't do any better at 1000 tries) -- undo after autorouting to return to the original state

In general, I would call this a UI issue: specifically in cases where all wiring was done in a given view, and then the autorouter doesn't complete in that view. I believe the user's intent is to use the autorouter to clean up the hand-routing, and frankly, our autorouter is not currently up to that task. Here are some suggestions:

-- When the autorouter gives up, put up a message to let the user know that connections have been lost, since it didn't complete (and there are no connections in the other views).

-- When the autorouter gives up, it should automatically return to the original state, saying that it failed to complete, and can't improve on the former state.

-- The autorouter should just state at to begin with that it probably can't improve on what has already been hand-routed, and should bail out immediately without doing anything.

Status: New
Owner: andre.knoerig@gmail.com
Mergedinto:

KjellMorgenstern commented 4 years ago

This issue is closed because the original information on google code was not be rescued before the service shut down. Some fixes have been done to the autorouter since then.