Why is the quoting in this wrong?
https://www.eevblog.com/forum/testgear/scope-wars/msg3115270/#msg3115270
My response is not nested correctly.
Reg
[quote author=gf link=topic=244895.msg3115242#msg3115242 date=1593644906]
[quote author=rhb link=topic=244895.msg3115206#msg3115206 date=1593643321]
Why do you have the 20 MHz BW filter turned on for this?
[/quote]
Sorry, the [b]AWG[/b] isn't faster :(
[quote]
A 1024 point FFT with a 1 ns sample interval has a 500 MHz Nyquist and 977 kHz RBW. With a 1024 pixel wide screen *every* sample can be shown. There is no interpolation needed.
[/quote]
Timebase is 20ns/div => ~1000 pixel = 200 ns, plus some headroom for zoom-in after stopping the capture. In the time domain display of the first image (-> step interpolation) you can see that the 1ns samples from the ADC are more than one pixel wide.
I'm pretty confident that the reported 12.5Gs/s FFT sampling rate is indeed the (upsampled) display buffer sampling rate for the selected timebase. Particularly in the first image, the spectrum beyond 1GHz matches the expected spectrum of the step-interpolation as shown in the time-domain trace.
[/quote]
Please put a 50 ohm thru termination on it and repost. A BNC tee with a 50 ohm terminator is "good enough". I'll address the rest later. Interpolation does *not* imply greater BW. Common knowledge if you resample via Fourier transform as I usually do.
Reg
Why do you have the 20 MHz BW filter turned on for this?
Sorry, the AWG isn't fasterQuoteA 1024 point FFT with a 1 ns sample interval has a 500 MHz Nyquist and 977 kHz RBW. With a 1024 pixel wide screen *every* sample can be shown. There is no interpolation needed.
Timebase is 20ns/div => ~1000 pixel = 200 ns, plus some headroom for zoom-in after stopping the capture. In the time domain display of the first image (-> step interpolation) you can see that the 1ns samples from the ADC are more than one pixel wide.
I'm pretty confident that the reported 12.5Gs/s FFT sampling rate is indeed the (upsampled) display buffer sampling rate for the selected timebase. Particularly in the first image, the spectrum beyond 1GHz matches the expected spectrum of the step-interpolation as shown in the time-domain trace.
Regarding the mysterious picture adds/replacements. I caught this problem in mid post that might give some clues to what is going on....
I am entering in a new post. I add a picture. In this case it is a picture of a mushroom in a photography focus stacking thread. I do the usual and add the pic, the post has not been sent.
In another window, I then scrolled through my old posts to find one that I intended to link into the post that is still open.
My eye caught that the pic of the mushroom had been substituted for a post of a graph in a corona virus thread - literally added to the post and when viewing the post, I can see that it was added and I could also see a notice:
There are attachments found, which you have attached before but not posted. These attachments are now attached to this post. If you do not want to include them in this post, you can remove them here.
So leaving an unattached photo (as when you are writing but have not submitted a post) is fair game to be inserted into any of ones posts that you view (not modify). Sounds nutty, but it looks like that is what just happened. I will complete the post and edit this message to see if it changes.
EDIT: as you can see, the pic in "limbo" got attached to this post. I did not add it to this post as per normal. Now that I know, I will be sure to have all my pics for a post lined up before opening any other windows or doing any other actions.
EDIT: I also see that the mushroom pic remained added to the corona virus post and bumped the original pic. I had to 'hand' correct that.
EDIT: and further, while the thumbnail pic attached to this post is the mushroom, the pic after the thumbnail is clicked, is the graph from the corona virus thread that I had to replace. I will log off hopefully clear the cache du jour and see if there is persistence....logging off/on makes no difference.
Pics in limbo are evil and get put in places that you don't want. Orphaning pics is the devils work
Regarding the mysterious picture adds/replacements. I caught this problem in mid post that might give some clues to what is going on....
I am entering in a new post. I add a picture. In this case it is a picture of a mushroom in a photography focus stacking thread. I do the usual and add the pic, the post has not been sent.
In another window, I then scrolled through my old posts to find one that I intended to link into the post that is still open.
My eye caught that the pic of the mushroom had been substituted for a post of a graph in a corona virus thread - literally added to the post and when viewing the post, I can see that it was added and I could also see a notice:
There are attachments found, which you have attached before but not posted. These attachments are now attached to this post. If you do not want to include them in this post, you can remove them here.
So leaving an unattached photo (as when you are writing but have not submitted a post) is fair game to be inserted into any of ones posts that you view (not modify). Sounds nutty, but it looks like that is what just happened. I will complete the post and edit this message to see if it changes.
EDIT: as you can see, the pic in "limbo" got attached to this post. I did not add it to this post as per normal. Now that I know, I will be sure to have all my pics for a post lined up before opening any other windows or doing any other actions.
EDIT: I also see that the mushroom pic remained added to the corona virus post and bumped the original pic. I had to 'hand' correct that.
EDIT: and further, while the thumbnail pic attached to this post is the mushroom, the pic after the thumbnail is clicked, is the graph from the corona virus thread that I had to replace. I will log off hopefully clear the cache du jour and see if there is persistence....logging off/on makes no difference.
Pics in limbo are evil and get put in places that you don't want. Orphaning pics is the devils workAnd now it's some other image, a still capture from a newscast. This problem is getting worse, it looks like to me.
I've encountered it here, among others:
https://www.eevblog.com/forum/chat/moisture-and-electronics/
https://www.eevblog.com/forum/repair/restore-dirtycorroded-ic-pins/
I've seen users posted images or attachments change after few hours to a different one from the same poster.
My rigoltime.png on here loads as xy.png
https://www.eevblog.com/forum/chat/does-a-capacitor-charges-smooth-or-in-stairs/msg3103617/#msg3103617


I've noticed that when attaching 2 or 3 images in-line, full size, the order of the attachments is not always respected... I then have to edit the post and change the AttachImage tags to make it work...
Good to know it's not just me... I thought I had somehow personally offended the Forum Gods.
Good Hunting, gnif. Hope you get it sorted soon.
mnem
Good to know it's not just me... I thought I had somehow personally offended the Forum Gods.
Good Hunting, gnif. Hope you get it sorted soon.
mnem

Not sure... like Gyro's example; I've had a post with a single image bork two older posts daisy-chain style. If I delete the borked pic to replace with the correct one, sometimes THAT pic will bork other older posts further down the thread. I think there's something messed up in how the database handles file pointers, m'self... but that's just drawn from hazy memories of Filesystems Forensics coursework in Uni almost 2 decades ago...
mnem
Not sure... like Gyro's example; I've had a post with a single image bork two older posts daisy-chain style. If I delete the borked pic to replace with the correct one, sometimes THAT pic will bork other older posts further down the thread. I think there's something messed up in how the database handles file pointers, m'self... but that's just drawn from hazy memories of Filesystems Forensics coursework in Uni almost 2 decades ago...
mnem
The messages and images may be served straight out of a database... no file system involved. It seems like a pretty ugly bug, though, that one message can affect another. Definitely things are being scrambled somewhere in the system, possibly incompatible libraries after a patch or update, or something like that.
gnif stated a couple pages back in the interest of transparency that SMF stores all attachments as a hash of the file contents and references them via a table. To me this sounded like pointers (base address and offset address in a table?) and I probably should've kept my mouth shut. 

Not sure... like Gyro's example; I've had a post with a single image bork two older posts daisy-chain style. If I delete the borked pic to replace with the correct one, sometimes THAT pic will bork other older posts further down the thread. I think there's something messed up in how the database handles file pointers, m'self... but that's just drawn from hazy memories of Filesystems Forensics coursework in Uni almost 2 decades ago...
mnem
The messages and images may be served straight out of a database... no file system involved. It seems like a pretty ugly bug, though, that one message can affect another. Definitely things are being scrambled somewhere in the system, possibly incompatible libraries after a patch or update, or something like that.
Yeah, that's me misremembering/misusing terminology last grokked over a decade ago.gnif stated a couple pages back in the interest of transparency that SMF stores all attachments as a hash of the file contents and references them via a table. To me this sounded like pointers (base address and offset address in a table?) and I probably should've kept my mouth shut.
If you don't use it you lose it.
mnem
*goes and stands in the corner*


Given that this seems to be happening to the same people repeatedly (I'm looking at you Mnem) and not to just everybody at random, can I suggest that the people who've experienced this post what combination of browser/version/platform that they are using? It has the flavour of being something like a change in platform javascript behaviour, perhaps tied to a particular recent version/update. If my hypothesis is right we should see some commonality between the setups of people that it's happening to, if it's wrong then we won't.

BTW, I have confirmed that it isn't just image files which get borked; I had a .pdf wind up in limbo the same way not too long ago.