-
Notifications
You must be signed in to change notification settings - Fork 36
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
Different Results For SSP and muSSP #16
Comments
Dear Kumarj95,
It is interesting. Can you send us example data so that we can diagnose the issue?
Guoqiang Yu
…________________________________
From: Kumarj95 ***@***.***>
Sent: Tuesday, October 22, 2024 6:30
To: yu-lab-vt/muSSP ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [yu-lab-vt/muSSP] Different Results For SSP and muSSP (Issue #16)
Hello Everyone,
Firstly I would like to thank the authors for this repository.
I have been trying to use the SSP solver included within this repository for my project. The reason I am using SSP over the titular muSSP is because the results from that algorithm seem to be closer to the old method I was using (https://developers.google.com/optimization/flow/mincostflow). It was a little confusing to me why the algorithms would produce different results (drastically different results at that).
I was wondering if anyone could help me out with this and provide some reading to better understand why this would be the case if it is not a bug in the code.
—
Reply to this email directly, view it on GitHub<#16>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK6247ZJSIZXW7VMNQDAJPLZ4V56XAVCNFSM6AAAAABQLE7XZ2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGYYDGNZZGEZDMOI>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hello, Sure, I have attached a sample graph.txt file. Here, if I use the muSSP solver I get the following output as my last line
Meanwhile if I use the SSP solver I get the following output as my last line
I have made some changes to the SSP solver, but they were related to being able to print out the solution in a text file, maybe I changed something important in the solver that causes this discrepancy. Please let me know if you are able to recreate this! |
Hello, After looking into it further, I was able to recreate the issue with a much smaller test file that might be beneficial for debugging (~2500 lines). In this case, the muSSP solver outputs the following:
While the SSP solver outputs the following:
Sorry for the large initial file. |
Hello, I just wanted to follow up to see if there were any updates on this! Thanks! |
Hi, Congchao,
Can you respond to this?
Guoqiang
…________________________________
From: Kumarj95 ***@***.***>
Sent: Saturday, November 23, 2024 1:25
To: yu-lab-vt/muSSP ***@***.***>
Cc: Yu Lab at Virginia Tech ***@***.***>; Comment ***@***.***>
Subject: Re: [yu-lab-vt/muSSP] Different Results For SSP and muSSP (Issue #16)
Hello,
I just wanted to follow up to see if there were any updates on this! Thanks!
—
Reply to this email directly, view it on GitHub<#16 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK6247Y42HUKZ7MIHN6S5AL2B5SG5AVCNFSM6AAAAABQLE7XZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGM2TKNZXHA>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hi Dr.Yu,
Sure. I did not notice that he uploaded examples for that. I will take a
look.
Best,
Congchao
…On Sat, Nov 23, 2024 at 9:57 PM Yu, Guoqiang ***@***.***> wrote:
Hi, Congchao,
Can you respond to this?
Guoqiang
------------------------------
*From:* Kumarj95 ***@***.***>
*Sent:* Saturday, November 23, 2024 1:25
*To:* yu-lab-vt/muSSP ***@***.***>
*Cc:* Yu Lab at Virginia Tech ***@***.***>; Comment <
***@***.***>
*Subject:* Re: [yu-lab-vt/muSSP] Different Results For SSP and muSSP
(Issue #16)
Hello,
I just wanted to follow up to see if there were any updates on this!
Thanks!
—
Reply to this email directly, view it on GitHub
<#16 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AK6247Y42HUKZ7MIHN6S5AL2B5SG5AVCNFSM6AAAAABQLE7XZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJUGM2TKNZXHA>
.
You are receiving this because you commented.Message ID:
<yu-lab-vt/muSSP/issues/16/2494355778 ***@***.***>
|
Hey Kumarj95, Sorry that I missed your uploaded example. I am currently out of town for Thanksgiving with my family and I will take a look right after I coming back. Thanks! Congchao |
No worries. Let me know if the second example I provided is still too tedious for debugging and I can try to produce something more manageable. Thanks again! |
Hello, I just wanted to follow up to see if there was an update on this. |
Hi, Congchao,
Can you look into the issue?
Guoqiang
…________________________________
From: Kumarj95 ***@***.***>
Sent: Saturday, December 21, 2024 3:06
To: yu-lab-vt/muSSP ***@***.***>
Cc: Yu Lab at Virginia Tech ***@***.***>; Comment ***@***.***>
Subject: Re: [yu-lab-vt/muSSP] Different Results For SSP and muSSP (Issue #16)
Hello,
I just wanted to follow up to see if there was an update on this.
—
Reply to this email directly, view it on GitHub<#16 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AK62475T4LPGWPKMSTH6SDT2GRTCXAVCNFSM6AAAAABQLE7XZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJXGU3TANRZGY>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Hey @Kumarj95 , sorry for the late reply. I have some urgent family issue recently. I double checked your graph. It indeed has different results using SSP vs. muSSP. I have not figured out how this could happen. Do you have a smaller graph to reproduce the results? This graph contains 500k+ arcs, I tried to print out intermediate results but it is very hard to debug with such big graph. Thanks! |
Hello @ccwang92 , I am sorry to hear about your family issue and appreciate you taking the time to look into this. |
Hello Everyone,
Firstly I would like to thank the authors for this repository.
I have been trying to use the SSP solver included within this repository for my project. The reason I am using SSP over the titular muSSP is because the results from that algorithm seem to be closer to the old method I was using (https://developers.google.com/optimization/flow/mincostflow). It was a little confusing to me why the algorithms would produce different results (drastically different results at that).
I was wondering if anyone could help me out with this and provide some reading to better understand why this would be the case if it is not a bug in the code.
The text was updated successfully, but these errors were encountered: