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
205 improve documentation on entry points #225
205 improve documentation on entry points #225
Conversation
Marked as in progress as @Anders-Markvardsen also mentions fitbenchmark_one_problem.py in the issue. But this looks up to date? |
This comment has been minimized.
This comment has been minimized.
Note
|
Thanks. As discussed removed for now not relevant block feature |
For the first issue I would expect it won't matter once the blocks are removed anyway (it'll change the code where the issue is raised.) but I'm not sure what could be causing the issue. It is working on my machine and Michaels when we've tried it.
I have just double checked the blocks on my laptop and it is also not working there so I'll remove it on monday. |
Running example_runScripts.py from anywhere remains broken, including for the location where a user most likely would like it from
This change degrades the user experience of FitBenchmarking. |
As a side when I run from the fitbenchmarking run directory: python setup.py install I get
which may not be related to this issue, but is a bug introduced into the install? Could you investigate where this bug originates from? |
@Anders-Markvardsen -- @AndrewLister-STFC is looking at this in #240. The fixes in #237 don't seem to work across all platforms, but as Travis doesn't run the example script at the moment this wasn't caught by the CI. |
The issue there is that you haven't specified an options file, and the default points to 'fitbenchmarking/fitbenchmarking_default_options.json', but I can change this to '../fitbenchmarking/fitbenchmarking_default_options.json' so it works from the example scripts directory instead. Originally it was using the location of the file and a relative path from there, which could be problematic also if things are installed in different places. Perhaps the best way to solve this is to have the default as the current dir (e.g. './fitbenchmarking_default_options.json'), and move the options file there. Either way, this was a change introduced in previous PR which was reviewed by @wathen, so a change to this should be a seperate issue. To get past the fact that you have been unable to run it you should pass the options file in as an arg: |
Co-Authored-By: Anders Markvardsen <anders.markvardsen@stfc.ac.uk>
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.
Manually testing of example scripts also. Reduction of in usability of running these is being work on separately.
Documentation improved and as a bonus nuke all references to out of date 'block' code
Description of Work
Fixes #205
Refactored do_benchmarking and edited docstrings to explain the code in a more understandable way.
Also contains commits for:
Testing Instructions