Comments (7)
jmmcd
commented on August 28, 2024
Yes -- and ponyge.py itself.
from ponyge2.
mikefenton
commented on August 28, 2024
Stats parser now lives in scripts folder. Ponyge.py was moved there, but there are conflicting ideas about where it should live (in /src or in /scripts). Answers on a postcard please.
from ponyge2.
mikefenton
commented on August 28, 2024
Stripped out and cleaned the experiment manager, added it back to the scripts folder. We now provide a basic experiment manager and stats parser. In terms of use, it's exactly the same as calling a normal PonyGE run (i.e. you can give params from the command line, through a params file, or by editing the params dict yourself). The number of runs can be set with --runs.
The only remaining question is whether or not to include the main ponyge.py file in the scripts folder or to leave it in \src. Thoughts?
from ponyge2.
dvpfagan
commented on August 28, 2024
Leave in src as it currently stands is my vote
…On 15 February 2017 at 15:04, Michael Fenton ***@***.***> wrote:
Stripped out and cleaned the experiment manager, added it back to the
scripts folder. We now provide a basic experiment manager and stats parser.
In terms of use, it's exactly the same as calling a normal PonyGE run (i.e.
you can give params from the command line, through a params file, or by
editing the params dict yourself). The number of runs can be set with
--runs.
The only remaining question is whether or not to include the main
ponyge.py file in the scripts folder or to leave it in \src. Thoughts?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/jmmcd/PonyGE2/issues/51#issuecomment-280034934>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA8zuiJdrMIxojVRS2xlQ1Hu3vCdv9pYks5rcxQYgaJpZM4MAcGY>
.
from ponyge2.
dvpfagan
commented on August 28, 2024
On 15 February 2017 at 15:06, David Fagan ***@***.***> wrote:
Leave in src as it currently stands is my vote
On 15 February 2017 at 15:04, Michael Fenton ***@***.***>
wrote:
> Stripped out and cleaned the experiment manager, added it back to the
> scripts folder. We now provide a basic experiment manager and stats parser.
> In terms of use, it's exactly the same as calling a normal PonyGE run (i.e.
> you can give params from the command line, through a params file, or by
> editing the params dict yourself). The number of runs can be set with
> --runs.
>
> The only remaining question is whether or not to include the main
> ponyge.py file in the scripts folder or to leave it in \src. Thoughts?
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/jmmcd/PonyGE2/issues/51#issuecomment-280034934>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AA8zuiJdrMIxojVRS2xlQ1Hu3vCdv9pYks5rcxQYgaJpZM4MAcGY>
> .
>
from ponyge2.
mikefenton
commented on August 28, 2024
The current setup looks good, closing this issue.
from ponyge2.
mikefenton
commented on August 28, 2024
Just adding to this to state that we currently need to save the scripts folder within the src directory. Various scripts use PonyGE packages located in src, and also interact with other scripts in scripts. Instead of constantly changing the path or adding new directories to the path, it just makes things a hell of a lot easier for everyone if we move the scripts folder inside the src directory. Everything works perfectly then.
This will not be an issue once PonyGE is an installable Python package, as we will be able to call it from everywhere. But this will require relative paths to be set, rather than os.getcwd()...
from ponyge2.
Related Issues (20)
- Default example doesn't run HOT 5
- Examples not working HOT 2
- `regex_improvement.txt` example - confusing message? HOT 1
- `seed_run_target.txt` example doesn't work
- Please help with solution min/max boundaries ❓ HOT 6
- Tree initialisation breaks when min = max depth
- Tree initialisation operators sometimes don't achieve stated depth
- Progsys with "Compare String Lengths" not giving valuable results
- Rethink if-else-classifier?
- progsys Digits problem
- progsys 'is' and 'is not' HOT 3
- missing contents of String Differences-Embed.txt HOT 1
- Statistics parser prog in Wiki incorrectly named
- save_state not working with multicore
- load_state not working with functions in custom module
- Post-processing python phenotypes is slow
- correct genome not returned when one of the codons is zero in the tree
- progsys count odds data
- Multi-objective optimisation is slow HOT 1
- Specifed moudle not found: fitness.xxx HOT 12
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ponyge2.