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

ipopt_l1 creates files in working directory #275

Open
Robbybp opened this issue Aug 8, 2024 · 4 comments
Open

ipopt_l1 creates files in working directory #275

Robbybp opened this issue Aug 8, 2024 · 4 comments
Assignees
Labels
Priority:Low Low Priority Issue or PR

Comments

@Robbybp
Copy link
Member

Robbybp commented Aug 8, 2024

It appears to automatically set the output_file option. To reproduce, write any Ipopt-compatible model.nl file to a fresh temp directory under the IDAES binary directory (e.g. ~/.idaes/bin). Run:

../ipopt_l1 model.nl -AMPL print_user_options=yes

I see the following options:

List of user-set options:                                                                                  

                                    Name   Value                used
                             output_file = 1723085945115811000   yes
                      print_user_options = yes                   yes

It also writes an l1EPR_timings.txt file to the working directory.

Opening this issue here for visibility, and I'm not sure where the ipopt_l1 source lives.

System info

Platform: ARM Mac
Binary version: 3.4.0
ipopt_l1 --version prints: Ipopt 3.13.3 (aarch64-apple-darwin22.5.0), ASL(20190605)

@ksbeattie ksbeattie added the Priority:Normal Normal Priority Issue or PR label Aug 8, 2024
@ksbeattie
Copy link
Member

@Robbybp, is this something you will be able to work on? Or who else might we assign this to?

@Robbybp
Copy link
Member Author

Robbybp commented Sep 5, 2024

David Thierry is the one who originally patched Ipopt to add the L1 restoration phase. I don't really use it, and don't know why or where in the code the files are getting written, so I can't be much use on this other than just pointing out the issue.

@Robbybp
Copy link
Member Author

Robbybp commented Sep 5, 2024

I would say this is a low priority unless users complain about it.

@ksbeattie ksbeattie added Priority:Low Low Priority Issue or PR and removed Priority:Normal Normal Priority Issue or PR labels Oct 3, 2024
@ksbeattie
Copy link
Member

@Robbybp, given your above comment, I'm taking this off the Nov release board.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority:Low Low Priority Issue or PR
Projects
None yet
Development

No branches or pull requests

2 participants