Skip to content
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

trsp and tsp name change to be more descriptive #427

Closed
cvvergara opened this issue Nov 14, 2015 · 12 comments
Closed

trsp and tsp name change to be more descriptive #427

cvvergara opened this issue Nov 14, 2015 · 12 comments

Comments

@cvvergara
Copy link
Member

Change the names to be more descriptive for example:
pgr_travelingSalesman
pgr_turnRestrictions
If someone likes short names they can wrap them on a function.
So, I can wrap it as:
pgr_vv <--- hey in spanish is vendedor viajante

@cvvergara cvvergara changed the title trsp and tsp name change trsp and tsp name change to be more descriptive Nov 14, 2015
@dkastl
Copy link
Member

dkastl commented Nov 18, 2015

pgr_travelingSalesperson is gender-neutral ;-)

@cvvergara
Copy link
Member Author

@dkastl
Wow, you got the hidden vv = Vicky Vergara

@cvvergara
Copy link
Member Author

currently TRSP and because of acronym usage, without looking at the documentation do you know what the acronym mean?
https://www.acronymfinder.com/TRSP.html

comparing with a well known acronym (TSP):
https://www.acronymfinder.com/TSP.html
you can find that TSP means Traveling Salesman Problem

So for TSP I am OK with using the acronym.

@cvvergara
Copy link
Member Author

about TRSP

I want to remove the acronym

SP = shortest path, not true with the current implementation
NOTE: all my examples are using the sample data of the documentation

Example: The shortest path from vertex 1 to vertex 1, well there should be no route

SELECT * FROM pgr_trsp(
    $$SELECT id::INTEGER, source::INTEGER, target::INTEGER, cost, reverse_cost FROM edge_table$$,
    1, 1,
    true,
    true,
    $$SELECT 100::float AS to_cost, 25::INTEGER AS target_id, '32, 33'::TEXT AS via_path$$
);

 seq | id1 | id2 | cost
-----+-----+-----+------
   0 |   1 |   1 |    1
   1 |   2 |   4 |    1
   2 |   5 |   8 |    1
   3 |   6 |   9 |    1
   4 |   9 |  16 |    1
   5 |   4 |   3 |    1
   6 |   3 |   2 |    1
   7 |   2 |   1 |    1
   8 |   1 |  -1 |    0
(9 rows)

So being "Shortest Path" a false statement.

Then pgr_TRP, pgr_TR ???

FYI, IDA BTAM WYDKWTM = For your information, I dislike acronyms, because they are meaningless when you don't now what they mean

the function's name options

  1. pgr_turnRestrictionsPath
  2. pgr_turnRestrictions

Note that the word "Shortest" is not there any more.
I will open two comments bellow, put your thumbs up to the name of your liking, (or open an issue with another name that you make up.

@cvvergara
Copy link
Member Author

Vote for
pgr_turnRestrictionsPath

@cvvergara
Copy link
Member Author

Vote for
pgr_turnRestrictions

@dkastl
Copy link
Member

dkastl commented Jun 12, 2018

Since the result is a path, it should be part of the name in my opinion.

What about the little change to pgr_turnRestrictedPath?

@woodbri
Copy link
Contributor

woodbri commented Jun 12, 2018 via email

@robe2
Copy link
Member

robe2 commented Jun 15, 2018

Sorry for the back and forth voting. I was undecided between pgr_turnRestrictionsPath and pgr_turnRestrictedPath. I still sort of am.

It seems like "Turn Restricted Shortest Path" term is used slightly more than "Turn Restrictions Shortest Path"

e.g you have it here as that
https://github.com/pgRouting/pgrouting/wiki/Turn-Restricted-Shortest-Path-(TRSP)

The docs seem to be a mixed flavor of both, so should be standardized to whatever naming you decide on:

https://docs.pgrouting.org/latest/en/pgr_trsp.html#trsp

@manikanta-kondeti
Copy link
Member

manikanta-kondeti commented Jun 17, 2018 via email

@cvvergara cvvergara removed this from the Release 3.0.0 milestone Jul 19, 2019
@cvvergara cvvergara added this to the Release 3.4.0 milestone Mar 25, 2022
@cvvergara
Copy link
Member Author

TRSP remains.
Almost a decade with the acronym been used on pgRouting that I think it is the best choice.
See TRSP family
For the new diversity of functions within this family

@cvvergara
Copy link
Member Author

Forgot to mention, related to #2238

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants