Jun 8, 2025
coding woes.
I can't code shit guys lmao. I might hire a team. i dunno.
Loading...
seen from United Kingdom
seen from Brazil
seen from United States
seen from Australia
seen from Germany
seen from China
seen from United States
seen from United States
seen from United States
seen from United States
seen from Malaysia
seen from China
seen from China
seen from China
seen from United States
seen from United States
seen from China
seen from United States
seen from Netherlands
seen from Sweden
coding woes.
I can't code shit guys lmao. I might hire a team. i dunno.
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Does anyone know how to fix the stupid problem with https in themes? Yes, I already madethem all https, so anything else? If I add so much as a period in my Alfred theme, it won’t let me do it and I’m anal about that blog and annoyed af.
Is there a way in the page inspection to scroll to the first TUMBLR messenger messages? If so, what am I looking for here?
Work Troubles
So today I was editing some code for the website I'm working on (not exactly true, but trying to explain the truth would probably be longer than the anecdote) So the code is more or less variations on a theme, just a list of items and their properties Unfortunately, I have to apply it all at once or the website decides to arrange them alphabetically instead of what i wanted to do So i check the code, and it comes up with an error. I know what the error means, there is a misplaced symbol in my code ($, * or the like) So i search for all the symbols i think might have sneaked their way in. I even look for doubles of characters and spaces where there shouldn't be No dice. This is becoming quite frustrating. I start to check small bits of the code at once (because it's technically one line [the website is a mess but that's another story] I have to cut and paste sections of the code) I check the first part, and it comes back with an error. I narrow it down further, and the error's still there I think to myself 'i must have found it!' and check over the code more closely Now, the items in this line are separated by the | character. I notice that when i cut this section up, i took the divider between the last item of this section and the next item Thinking little of it, i remove the extra |. I then come to a horrifying realisation. Scrolling down all the way to the bottom of the original code, i see right at the end, there's a |. I remove it, check for errors and this time it comes back clean. This was an annoyingly long time of troubleshooting, which was a 2 second fix. FML
my code is a fool because I am a fool, but I am trying not to be a fool so that’s something
Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
brain is chugging at code problems and I have rewritten like only five lines because there are too many things I’m trying to fix at once aaaaaaaaa
Lovely great just gotta run the script all over again bc the list of observation IDs that was being made to query and download from HEASARC was skipping the first line and it heckin’ crashed itself because it only read one line in the data.dat file so it wrote nothing .
np.loadtxt takes an argument called skiprows that I used to skip the first two rows in the file that the perl script makes, they’re just for formatting and aren’t important and make my code crash. HowEVER I was accounting for this twice when indexing the for loop writing the download script, because I wrote:
for i in range(1,len(obslist)-1):
when it should have started at zero and run the full list, like this:
for i in range(len(obslist)):
which means my code has been skipping the first observation for every galaxy. So now the sucker’s running AGAIN. *deep inhale*
Shit man so much progress today!!
I had a zoom conference with L, the survey PI and she was able to help me sort through some code problems, set up astroconda and start using environments, and get the pretty pictures closer to something we’d post on the website!
My code crashed last night after about five galaxies, and by checking the names and the download scripts we figured out that SCULPTOR-DE1 hadn’t actually been observed at all since the wrong coordinates had been given to the satellite. We ended up finding at least three other galaxies in the input list that had not been observed enough to build images of them, so now I should be able to run it to completion barring anything else like this happening.
We’re back to calculating the mode of the image pixels instead of zeroing out any pixels clipped by sigma_clip.
NGC0045 has a huge bright star in the field that’s got a very red halo around it in the pretty picture, but astronomers are used to those kinds of artifacts so I may be cleared to leave it like that. The penultimate iteration of pretty pictures cut out a lot of structure in the image, and now all of that is still visible with enough of the background present to do science with using the data cube made with make_rgb_cube.
L passed on a couple of tools she’s built called offset_mosaic and config_uvot_mosaic to build better science images with. It turns out the data cubes that I’m making the pretty pictures out of are also useful for photometry science, which is what I’ll get to do next! Keeping in some of the background instead of making it entirely black will allow us to do better photometry in the future, since we have to make an estimate of what the background is to compare it to bright objects like galaxies.
Just sticking around to make sure the code will run through one galaxy and move on to the next properly, and then I get to go home! In the snow! Holy shit!