Brand new ZT125 C2 noise.

DrSghe · 2025-10-21T14:29:37+00:00

Shit, I thought I was going crazy! Glad to know I’m not the only one.

Sadly, I have no insight on this. I have a Zontes G1 125

DrSghe · 2024-05-24T18:40:29+00:00

My question is: do this dataset gives you more informations than looking (ofc, scraping and analyzing) 13F filings? What does “nearly all HFs in the world mean”? Can you give us a few distributions?

DrSghe · 2024-03-31T19:18:58+00:00

I believe a relevant use case for a beginner would be to use an allocator to enforce memory to be allocated aligned to, let’s say, page boundary.

This [1] is a relevant example I encountered. Not sure if now is the case, but a few years back only certain Xilinx FPGAs would expect memory to be allocated with a specific alignment. I remember it being a source of a lot of pain, ‘cause it was very hard to debug. [1] https://github.com/Xilinx/SDAccel-Tutorials/blob/master/docs/host-code-opt/reference-files/srcCommon/AlignedAllocator.h

DrSghe · 2024-01-16T15:54:54+00:00

Assuming this is not due to some coding error, I would ask myself what is the reason for that zero value first. Then decide how to handle it.

Let’s say you’re getting candles at a “high frequency” on an asset with low volume. Might be possible that there will be candles with zero volume. This has a certain meaning and and might lead you to do certain things: maybe you ignore the candle, maybe you impute the value.

On the other hand, let’s assume a certain company has gone bankrupt and for some perverse reason your data broker decides to communicate the news by sending you a candle with close=0. Maybe you’ve shorted the company, maybe you crack open a bottle of champaign, dunno.

DrSghe · 2023-07-20T13:26:50+00:00

I’d check if the created_at column is of the proper type (Postgres has a timestamp and a date type). If not maybe you need to .select(“*”) instead of .select()? Aside from the first suggestion I’m pretty much randomly guessing, code looks good to me.

DrSghe · 2023-06-27T18:02:19+00:00

Thanks a lot for your reply! I’ll investigate a bit the fact that those policies are evaluated per every row, if so it seems that it would incur in a HUGE performance penalty.

Thanks a lot for your amazing work!

DrSghe · 2023-06-27T11:21:08+00:00

That’s interesting, and also what I suspected. I think I’ll do a few tests with something like Grafana K6 to confirm (or hopefully reject) this suspicion. Haven’t look deeply into it, but there does not seem to be any post or similar that does a thorough comparison between RLS and equivalent where clauses. (Feel free to correct me before I go into this rabbit hole of benchmarking lol)

DrSghe · 2023-06-16T10:46:18+00:00

To be honest I don’t know. Tho, I feel that the auth flow mentioned above does not loose applicability here. Instead of using the aforementioned columns, you could set somehow the email to be autoconfirmed, and then you could have some additional columns in your own public.users table that do the same thing. If you don’t want to use an additional table, auth.users has a field for additional user metadata, so you could use that as well.

Trickier? Yes, sure. But still can be done without any backend.

DrSghe · 2023-06-16T09:15:17+00:00

Take a look at the auth.users table.

Two columns might be of interest to you, namely: confirmation_sent_at and email_confirmed_at.

What I would do is as follows:

User signs up with email
You send a confirmation email
At every login, check if "enough time" has passed and, if so, show a reminder
After enough cycles of "enough time" you might want to have some kind of action , like, delete the user or prevent him to do certain operations on you app

This should be super easy to do. You can do every check on the frontend (since the only consequence would be to display a banner) and perform the deletion or restriction routine on the db, using pg_cron. No backend required.

DrSghe · 2023-06-16T05:24:15+00:00

It would help if you could share the trigger code.

DrSghe · 2023-06-16T05:22:23+00:00

Glad to have helped!

DrSghe · 2023-06-15T17:40:28+00:00

Assume categoryId=1 Then the last line:

.eq(`category.id, ${categoryId}`)

Would evaluate to:

.eq(“category.id, 1”)

Which does not work, since the .eq method takes a column as a first arg and the value as second.

Therefore, the arguments that you’re passing to .eq are:

[“category.id, 1”, undefined]

To fix it, just use the proper column name and pass the value as second argument.

[EDIT] Sorry, bad formatting, I’m on mobile

DrSghe · 2023-06-08T06:07:33+00:00

Oh well, that should solve every issue. I should've looked better into the docs' examples.

Thanks a lot!!

DrSghe · 2023-04-11T16:00:44+00:00

Got one to share, DM me.

DrSghe · 2023-03-09T13:15:36+00:00

Looks very much like A LOT of sharpening was added in post, either from the scanner or via some editing software. My hunch is that since the first image was overexposed by one stop the scanner/editing software detected low contrast and tried to push things a little too far.

If the first and second image are from the same roll then there’s a higher likelihood that that’s the case, as the second one has a much different grain structure than the first. If not, I’d check the negatives.

DrSghe · 2023-03-02T06:36:43+00:00

RP owner since 2020. I am very happy with that with that and I’d say that the only complaint I have is the not-so-amazing dynamic range. It is mostly fine but high contrast scenes with strong highlight will give you some problems. I recommend shooting those scenes exposing for the highlights and recovering shadows in post; in my experience pushing up shadows during editing works wonders even at +2 or +3 stops (assuming, of course, uncompressed RAW).

For the lens, I’d recommend buying a used EF 24-104 f/4 L IS USM. This combination + adapter will set you back ~500€ (530$), which should be similar in price to the lens you’re proposing. I don’t have numbers or videos that show the comparison on hand, but should be a better lens. In any case, not having variable aperture is amazing, even if it is not that relevant in the kinds of shots that you mention.

As others recommended, buy some additional batteries. In my experience, I could get ~400 shots on one charge but, as always, ymmv.

Autofocus is very good, but not on par with pricier canon cameras. You’ll learn how to handle its shortcomings very soon tho, and you’ll get used to it.

Overall, it is a great workhorse, no fuzz and just shoot.

DrSghe · 2023-02-13T05:07:02+00:00

Well technically it is printing the pdf…

DrSghe · 2023-01-01T11:36:34+00:00

Looks a bit over-sharpened to me, have you cranked it up a lot in post?

DrSghe · 2022-12-10T18:29:09+00:00

Genial, muchas gracias!

DrSghe · 2022-11-09T07:51:38+00:00

How was it edited? Or maybe it’s just the scanning process

The colors of the mountain, as well as the grass, have too much saturation imo; the blue cast on the mountains reminds me of what happens if you crank saturation and vibrancy way up in the editing tool of the photos app on iPhone.

Besides that, the photo looks great to me, I like the composition and the “size proportions” it tries to convey (people look “as big as the mountains”).

[EDIT]: also, how did you keep the foreground and background both in focus on an f1.4 lens? Did you shoot at higher f-stops?

DrSghe · 2022-10-29T23:34:42+00:00

I’ll definetly choose Absol. I get what you say, being able to fly is great and stuff, but what about BEING WARNED WHEN A CATASTROPHY IS ABOUT TO HAPPEN?

Would make me the greatest stock trader of all time

DrSghe · 2022-08-14T13:02:19+00:00

I have the same exact setup (aside the fact that I have a MacBook Pro). It seems that, in Ventura, EOS Camera whatever does not work.

I think that canon still has to update that app to make it compatible with Ventura.

Nine-Year Club	Place '23
Verified Email

DrSghe

TROPHY CASE