let merged = {...obj1, ...obj2}; See (1) which has 2808 votes.
(1) https://stackoverflow.com/questions/171251/how-can-i-merge-p...62 karma · joined December 30, 2019
let merged = {...obj1, ...obj2}; See (1) which has 2808 votes.
(1) https://stackoverflow.com/questions/171251/how-can-i-merge-p... for (const name of v.classes)
if (!el.classList.contains(name)) el.classList.add(name)
for (const name of el.classList)
if (!v.classes.includes(name)) el.classList.remove(name)
Why the standard decided to make classList read-only?Could ele.className=(v.classes).join(" ") be a valid and performant solution?, perhaps is to avoid the string to token traslation for performance reasons?, then why don't they include a classList.set method?
In (1) there is a full example of using the two step strategy but using more labeled data to obtain 92% of accuracy. Someone can try changing the second part to use only ten labels for the classifying part and share results?
(1) https://www.datacamp.com/community/tutorials/autoencoder-cla...
Edited: I found a deep analysis in (2), in short for CIFAR 10 the VAE semi-supervised learning approach provides poor results, but the author has not used augmentation!
(2) http://bjlkeng.github.io/posts/semi-supervised-learning-with...
Edited: In a recent article (1) it seems that multicast is better than SFU in webrtc. In the PhD. Thesis (2) a hybrid model is used: Hybrid multicast-unicast video streaming over heterogenous cellular networks.
(1)https://ieeexplore.ieee.org/document/8811590 (2) https://summit.sfu.ca/item/16802
Edited: I must learn something about multicast in IPv6, the idea seems interesting.
Edited: It seem that RtcDataChannel can be used with SFU, example LiveSwitch in 2018, but they don't use multiple destination datagrams (3)
More on similar proposal (2).
(1) IPv4 Option for Sender Directed Multi-Destination Delivery. The Selective Directed Broadcast Mode (SDBM) is an integral part of the U.S. Army standard for tactical data communication networks as defined in MIL-STD-188-220().
(2) https://www.researchgate.net/publication/238663190_IPv4_Opti...
(3) https://www.frozenmountain.com/developers/blog/archive/indus...
In my very humble opinion, I would suggest to reserve some address space in IPv6 for rtc, so that a peer is able to adopt a new special ip reserved for rtc. Nothing new under the sun, in 2014 someone comment along this line of thought (2) and (3).
So what are we waiting for?
(1) https://webrtcglossary.com/ (2) https://www.quora.com/Will-the-IPv6-result-in-the-death-of-S...
(3) 2014, AshleysBrain, https://news.ycombinator.com/item?id=7496986 I think the solution is IPv6. Once every device on the Internet is uniquely addressable again, we can do away with these NAT hacks and two endpoints should be able to reliably connect to each other again, no matter where they are. Of course, that's assuming we don't get more short-sighted engineering that breaks things again...
argmax([x,y]) = (sign(x[0]-x[1])+1)/2
Going beyond continuous functions, can deep learning be used for primality test?
(1) https://en.wikipedia.org/wiki/Universal_approximation_theore...
(1) https://datascience.stackexchange.com/questions/56676/can-ma...
If you can convince the judge that taking the screenshot has other purpose then GDPR doesn't apply.
From (2): The WP29 outlines that a DPIA is likely to be required if «a company systematically monitor(s) its employees’ activities, including the monitoring of the employees’ work station, internet activity» since it implies a «systematic monitoring and data concerning vulnerable data subjects» (23), form GDPR and Personal Data Protection in the Employment Context CLAUDIA OGRISEG
In (1) at point 8: the employeer has to inform the employee about: (i) whether and when monitoring is applied. (ii) the purpose of data processing, (iii) the means used for data processing.
https://legalict.com/factsheets/privacy-monitoring-work-gdpr...
Point 2) What king of personal data does an employer process, includes: Remote management of all mobile devices, such as phones and laptops;
(1) http://blog.plataformatec.com.br/2019/10/kubernetes-and-the-...
(1) https://github.com/percyliang/cs229t/blob/master/lectures/no...
from (3) .Ransomware Gangs to Stop Attacking Health Orgs During Pandemic
(1) https://www.bleepingcomputer.com/news/security/netwalker-ran...
(2) https://www.bleepingcomputer.com/news/security/nation-backed...
(3) https://www.bleepingcomputer.com/news/security/ransomware-ga...
Also TP + FN = Prevalence of the desease, but using P for prevalence and for positive creates a lot of confusion in a wikipedia page to explain a concept.
My plea is that I don't want people to get confused. On top of it there is a warning on that page of wikipedia: This article may be too technical for most readers to understand. I couldn't understand why they used that notation. So I ask to delete that page because is going to confuse people.
Afortunately there is the following page in which they only use TP,FP, TN, FN that is true/false and positive/negative. So replace that page with https://en.wikipedia.org/wiki/Precision_and_recall or change notation. Please.
P = TP + FN is something that I would never put on paper.
Edited, (1) is a good first step at shapely value theory and applications:
(1) https://medium.com/datalab-log/understanding-the-impact-of-f...
http://www-sop.inria.fr/cafe/Manuel.Bronstein/pmint/index.ht...
Clearly, if your generator for equations is limited the system can learn the dictionary lhs (integral) => rhs (derivative) to go rhs => lhs. (integrate)
Problem P1 is locally similar to P2 if (method,efficiency,P1) meassured in computation time is similar to (method,efficiency,P2) for method in a local space of methods. The method should learn to classify both problem and methods, that's similar to learning words and context words in NLP or matrix factorization in recommendation systems. To sample the (space,method,efficiency) space one need huge resources.
Added: To compare a pair of (method,problem) some stardardization should be used, for linear problems related to solving linear systems the condition number of the coefficiency matrix should be used as a feature for standardization and, for example in SAT an heuristic using the number of clauses and variables should be used for estimating the complexity and normalization of problems. So the preprocessing step should use the best known heuristic for solving the problem and estimating its complexity as both a feature and a method for normalization. Heuristic and DL for TSP is approaching SOTA (but concord is better yet).
Finally perhaps some encoding about how the heuristic was obtained could be used as a feature of the problem (heuristic from minimum spanning tree, branch and bound, dynamic programming, recurrence, memoization, hill climbing, ...) as an enumerative type.
So some problems for preprocessing are: 1) What is a good heuristic for solving this problem. 2) What is a good heuristic for bounding or estimating its complexity. 3) How can you use those heuristics to standardize or normalize its complexity. 4) How big should be the problem so that the assymptotic complexity takes over the noise of small problems. 5) How do you encode the different types of heuristics. 6) How do you value the sequential versus parallel method for solving the problem.
Finally, I wonder if once a problem is autoencoded then if some kind of curvature could be defined, that curvature should be related to the average complexity of a local space of problems, also transitions like in graph problems should be feautured. The idea is using gems of features to allow the system to combine those or discover new better features. Curvature could be used for clustering problem that is for classification of types of problems. For example all preprocessed problems for solving a linear system should be normalize to have similar efficiency when using the family F of learning methods otherwise a feature is introduced for further normalization. For example some problems could require to estimate the number of local extrema and the flat (zero curvature extend of those zones)
It should be nice using a more informative language for giving advice. If this story is tagged as "popular story for dummies" I would feel we are making real progress.
Just one of Minsky great ideas related to reinforcement learning: The credit assignment problem:How do you distribute credit for success among the many decisions that may have been involved in producing it?, in "Steps Toward Artificial Intelligence" (Minsky, 1961): All of the methods we discuss in this book are, in a sense, directed toward solving this problem.
That book is linked from HN and it has just one comment, so I think that NDNS, no dumb nerd stories, will never become popular.
(1) https://news.ycombinator.com/item?id=10972522
More from (2) Minsky in 1951 built the world's first “randomly wired neural network learning machine,” called the stochastic neural-analog reinforcement computer (snarc)
https://www.geek.com/blurb/marvin-minsky-ai-has-been-brain-d...
A fair paper: Exploring Randomly Wired Neural Network for Image Recognition.
Was Sussan at the edge of envisioning deep learning?, then in fact the room has dissapeared!
(1) https://news.ycombinator.com/item?id=19344146
Edited: Added in the comments of that post there is a reference to pocorgtfo16.pdf: is valid as a PDF document, a ZIP archive, and a Bash script that runs a Python webserver which hosts Kaitai Struct’s WebIDE which, allows you to view the file’s own annotated bytes. The zip archive has further resources to insane reversing deep dives, code to study and more.
Scala avoids the biggest pitfall of multiple inheritance elegantly, by only allowing one parent to have a constructor; classes may only be the first parent, and traits can't have constructors that take arguments. Unfortunately this doesn't mean they don't need to be initialized; in particular, vals in a mixed-in trait will be null if you try to access them in an earlier constructor.[2] As with any null, in the worst cases you may not get an error until much later on.
But sadly I could not obtain a clear picture of what is the difference between their detector and a baseline one. There are some minor points and references about upsampling, downsampling, resizing, cropping and fourier spectra comparison across generators, but those seems to be just comments and comparison and not crucial points in the construction of the detector. Furthermore data augmentation doesn't play a big role, they say that it usually improves (a little) the detector.
As a math person I like to get some more meat from papers, but here it seems that little tricks allow then to win the game. Perhaps that is the way (little or no math involved) to make advances. Well, at least they say that shallow methods modify the fingerprint of the fourier spectra so that now you can't detect which is the generator of the image.
Perhaps the "universal word" was what captured my attention.
(1) We show that when the correct steps are taken, classifiers are indeed robust to common operations such as JPEG compression, blurring, and resizing.
(2) When using Photoshop like methods the detector performs at chance (is useless).
Edited: See (1)for some related ideas: A Safe Approximation for Kolmogorov Complexity
(1) https://link.springer.com/chapter/10.1007/978-3-319-11662-4_...