1
Repair / Re: Help with bricked APC UPS SMT1500
« Last post by DavidAlfa on Today at 07:34:00 pm ».enc might be anything.
But actual field studies, conducted in real life have failed to show masking actually works in practice. Fair enough, it doesn't prove a negative, but it certainly doesn't prove positive either.It isn't. I didn't say that it's proof that masks and keeping 2m apart don't work, just that there's no strong evidence they do. The Cochrane review into masking found it to be inconclusive and as far as I'm aware no studies have been conducted into whether keeping 2m apart does anything to reduce the spread or not. And why 2m? Perhaps 1m would have done? Or maybe we needed to keep 3m or 5m apart? Where's the evidence?
Then there's all the other misinformation exaggerating the efficacy of masks, keeping 2m apart etc. which lacked rigorous evidence to support and the authoritarian policies copied from Communist China. It appears as though the public health authorities did their level best to destroy their reputation.
And what proof is there that distancing does not work?
It would be different if we were just advised to wear masks and keep 2m apart. That wouldn't have been ideal, given the lack of evidence, but the fact we were forced to, under pain of a fine, is disgusting. If the authorities are going to punish people for breaking rules, then there needs to be extremely strong evidence to support them in the first place.
Both distancing and masks rely on basic physics! You want a study? go an throw some tennis balls and notice that the further they go the closer to the ground they get. And that if you through them as several layers of nets they will no go nearly as far. What you are asking for in the equivalent to arguing about the distance to the moon because a tape measure was not used.
Repeat infections will do the same.Do you realise that if you keep taking a vaccine you loose immunity to the disease it is for?FFS It is exactly the other way around! Vaccines train your immune system against virusses. For mutating virusses, you'll need regular updates to stay current. It is like airplane pilots taking courses in a simulator to learn what to do in an emergency situation for a different airplane.
Except being sceptical of COVID and seasonal influenza boosters is not a fringe position, based on conspiracy theories. I don't appeal to authority so won't post any names, but there are plenty of highly esteemed medical experts who are respiratory virus/mRNA vaccine septics.There arge instances of immunization not working as intended and causing untoward reactions when the patient gets infected. Past RSV immunizations are an example.
No one is disputing that a small number of people will have adverse reactions. It does happen. But rather, for the vast majority of the population (i.e.: almost everyone), it has a positive impact overall.
You're wasting your time; in the words of Simon and Garfunkel, "The man hears what he wants to hear and disregards the rest".
This is why I don't participate in these types of thread, they just attract the conspiracy nuts, and others, all of whom have apparently zero understanding of epidemiology, or statisitics and how to interpret them.
Sure, but my aim isn't to change the minds of those who are set in their ways, rather try to educate those who are willing to listen and consider facts from different sources. If we let the conspiracies run wild, there would be nothing other than "vaccines are poison" and "5G activates the nano-robots".
But yes you're right, these types of threads generally have a finite life, after which it just becomes utter chaos.
I do that differently. I sample the stack pointer inside a timer interrupt and update the 'lowest stack address' variable when it is below the previous value. This gives a very quick idea of worst case stack usage without going through a lot memory. I do admit I 'stole' this idea from someone else though. Clearing memory to zero is a very safe thing to do as 0 or NULL is often regarded as the end of something or invalid. Setting the stack memory area to a different value, could cause more problems than is solves. Also, used stack space is likely to be unequal to zero.Probably ST wanted to hide the init as part of the HAL or avoid confusion and have everything initialised before calling main. In my own code these two lines do all the required initialisation:Code: [Select]memset(_data, 0, _stack_end - __bss_start__-32); //clear memory including stack
if (_edata!=_data) memcpy(_data, _datastart , _edata-_data); //copy initialised variables if present
I make it a point to clear the stack as well. In some rare cases old data on the stack can trigger very rare bugs in combination with (for example) an array / pointer going out of bounds even across resets. Clearing the stack results in consistent behaviour of the fault.
clearing the stack (or setting it to some magic number) can give you an hint on how much is being used by examining the stack area