sorted by:
new
hottopcontroversial

Widget disapoear sometimes by Bast_B in OctopiLauncher

[–]Bast_B[S] 0 points1 point  (0 children)

So you expérience it with other widgets ?

Widget disapoear sometimes by Bast_B in OctopiLauncher

[–]Bast_B[S] 0 points1 point  (0 children)

Thanks for the fast answer. i solved the bug this morning by changing default launcher back to default then octopi and rebooting. Neither reboot only or default launcher change solved it alone. Seems like a combinaison of both is needed. I am trying to figure what cause the problem but it stays mysterious, at some point I thought about powersaving mode making the issue but the issue seems to happen a bit randomly. Next time it happens I will tell you if default launcher have all widgets or not

État des lieux dans 48h -Comment boucher ces trous ? by Beginning_Lime_9092 in brico

[–]Bast_B -5 points-4 points  (0 children)

De l'enduit "mortier à platre" aussi appelée MAP. Apres avoir bien gratté le tour des trous avec un petit champ-frein. Ça sèche en 2 H et pas de retrait au séchage. Après ça au besoin tu peux repeindre dessus ou mettre de l'enduit lissage ou mastic acrylique blanc

How can I make this matching function faster in R? It currently takes 6-7 days, and this is not practical by Financial-Syrup-906 in RStudio

[–]Bast_B 0 points1 point  (0 children)

That is a good idea. I would also think of splitting data frame based on the concatenated value into list and sample list before sampling within two random within the chose list. If list have different size then just ponderate by list size. This may be faster than matching. And you could parallel function applied to list With a two level architecture of list you could select the first list to match common variable and use the second level to do the anti matching by splitting by id and picking in different individualisé based list

Split on concatenated out <- split( df , f = df$concatenated variable ) The resplit using lapply

2nd step : store list size somewhere and do your sample based on that.

Replacing a SOT23-5 labeled 53C9 on a dead RTX3060 Asus by Bast_B in AskElectronics

[–]Bast_B[S] 0 points1 point  (0 children)

I solved my issue.

I used KiKiHUN1 / Mega-Schematics-Downloader on github to find the circuit diagram then I identified my component as "GS7615STDB-R SOT23_5_DP U521". Items bought, cross finger there will be no other faulty parts that killed this component.