-
Notifications
You must be signed in to change notification settings - Fork 4
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
Regenerated some worlds using the numpy-branch. #1
Conversation
I am not sure if this is done correctly or not. Right now the tests on my system don't go through, so I will have to check some more things. Hold on. EDIT: I thought I generated a pickle-file (28070), but for some reason it is being read with protobuf - and that fails. Do you have any hints? I used the following parameters: EDIT: According to drawing_functions_test.py it should be a protobuf-file. xP |
Now I am left with a dozen blessed_pixel-errors. How do I deal with those? I assume I have to replace the images, too. But since they are named a bit strange I am not sure. To clarify: Before I updated the world I had one blessed-pixel error. Hence I think that it is not the drawing functions but the world generation that changed (probably due to the change to the seeding done here: |
Ok, I updated the images. The pickle-save is left untouched and that is now the cause for the only failed test that remains. But since it differs depending on the used version of Python there wouldn't be much use in regenerating it anyway. (Because then other peoples tests would fail.)
|
Summary: I think I am done with this. It was a bit difficult to figure out what to do, though. |
I noticed that I regenerated plates_279.world, which is actually a pickle-file. So I guess that file would break Python 2-compatibility. A possible solution is suggested here: |
Yup, two problems.
We solve the 1st one by writting tests specific to python version that created the pickle file. The second one requires that we replace all the old pickle worlds and images in worldengine-data. |
The tests-problem seems to be easy to solve. I can generate the Python 3-worlds, too. |
So once this branch is merged, the tests in worldengine will work again? Also I noticed this when looking at the "files changed": tests/images/temperature_28070.png |
I noticed that, too. I had not changed anything about the temperature-file yet, so I am not sure why it looks so different. Maybe it is just the differently-shaped world that is responsible? |
The temperature image here also looks a lot noisier: That can't be a coincidence, can it? Did something about the temperature-algorithm change within the last ~4 months? Are my changes responsible for this? (I don't think I ever generated a map like that, though. Not even with the release-version. I might have to go back and check that.) |
Could that depends on the elevation? I think it affects the temperature |
Yes, it does. Flat areas might influence it. However, when I ran the (slightly modified) temperature-generation here Mindwerks/worldengine#143 all of the outputs I got were much less random than the one linked to above. |
We'll get back to this later. I'm happy to merge this to get our tests back in order. :) You OK with this @ftomassetti ? |
Yes, go on! |
Regenerated some worlds using the numpy-branch.
I hope this is what I was supposed to do.