Window

window

Running Cisco pyATS on Windows 11 Really Helped Me Brush Up My Python Fundamentals

Authors:
(1) Guillaume Staerman, INRIA, CEA, Univ. Paris-Saclay, France;
(2) Marta Campi, CERIAH, Institut de l’Audition, Institut Pasteur, France;
(3) Gareth W. Peters, Department of Statistics & Applied Probability, University of California Santa Barbara, USA. Table of Links Abstract and 1. Introduction 2. Background & Preliminaries 2.1. Functional Isolation Forest 2.2. The Signature Method 3. Signature Isolation Forest Method 4. Numerical Experiments 4.1. Parameters Sensitivity Analysis 4.2. Advantages of (K-)SIF over FIF 4.3. Real-data Anomaly Detection Benchmark 5. Discussion & Conclusion, Impact Statements, and References Appendix A. Additional Information About the Signature B. K-SIF and SIF Algorithms C. Additional Numerical Experiments 4.1. Parameters Sensitivity Analysis We investigate the behavior of K-SIF and SIF with respect to their two main parameters: the depth of the signature k and the number of split windows ω. For the sake of place, the experiment on the depth is postponed in Section C.1 in the Appendix. The Role of the Signature Split Window. The number of split windows allows the extraction of information over specific intervals (randomly selected) of the underlying data. Thus, at each tree node, the focus will be on a particular portion of the data, which is the same across all the sample curves for comparison purposes. This approach ensures that the analysis is performed on comparable sections of the data, providing a systematic way to examine and compare different intervals or features across the sample curves. We explore the role of this parameter with two different datasets that reproduce two types of anomaly scenarios. The first considers isolated anomalies in a small interval, while the second contains persistent ones across all the function parametrization. In this way, we observe the behavior of K-SIF and SIF with respect to different types of anomalies. The first dataset is constructed as follows. We simulate 100 constant functions. We then select at random 90% of these curves and Gaussian noise on a sub-interval; for the remaining 10% of the curves, we add Gaussian noise on another sub-interval, different from the first one. More precisely: • 90% of the curves, considered as normal, are generated according to with ε(t) ∼ N (0, 1), b ∼ U([0, 100]) and U representing the uniform distribution. • 10% of the curves, considered as abnormal, are generated according to where ε(t) ∼ N (0, 1) and b ∼ U([0, 100]). We simulate at random 90% of the paths with µ = 0, σ = 0.5, and consider them as normal data. Then, the remaining 10% are simulated with drift µ = 0.2, standard deviation σ = 0.4, and considered abnormal data. We compute K-SIF with different numbers of split windows, varying from 1 to 10, with a truncation level set equal to 2 and N = 1, 000 the number of trees. The experiment is repeated 100 times, and we report the averaged AUC under the ROC curves in Figure 1 for both datasets and three pre-selected dictionaries. For the first dataset, where anomalies manifest in a small portion of the functions, increasing the number of splits significantly enhances the algorithm’s performance in detecting anomalies. The performance improvement shows a plateau after nine split windows. In the case of the second dataset with persistent anomalies, a higher number of split windows has a marginal impact on the algorithm’s performance, maintaining satisfactory results. Therefore, without prior knowledge about the data, opting for a relatively high number of split windows, such as 10, would ensure robust performance in both scenarios. Additionally, a more significant number of split windows enables the computation of the signature on a smaller portion of the functions, leading to improved computational efficiency. This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Guillaume Staerman, INRIA, CEA, Univ. Paris-Saclay, France; (2) Marta Campi, CERIAH, Institut de l’Audition, Institut Pasteur, France; (3) Gareth W. Peters, Department of Statistics & Applied Probability, University of California Santa Barbara, USA. Authors: Authors: (1) Guillaume Staerman, INRIA, CEA, Univ. Paris-Saclay, France; (2) Marta Campi, CERIAH, Institut de l’Audition, Institut Pasteur, France; (3) Gareth W. Peters, Department of Statistics & Applied Probability, University of California Santa Barbara, USA. Table of Links Abstract and 1. Introduction Abstract and 1. Introduction 2. Background & Preliminaries 2. Background & Preliminaries 2.1. Functional Isolation Forest 2.1. Functional Isolation Forest 2.2. The Signature Method 2.2. The Signature Method 3. Signature Isolation Forest Method 3. Signature Isolation Forest Method 4. Numerical Experiments 4. Numerical Experiments 4.1. Parameters Sensitivity Analysis 4.1. Parameters Sensitivity Analysis 4.2. Advantages of (K-)SIF over FIF 4.2. Advantages of (K-)SIF over FIF 4.3. Real-data Anomaly Detection Benchmark 4.3. Real-data Anomaly Detection Benchmark 5. Discussion & Conclusion, Impact Statements, and References 5. Discussion & Conclusion, Impact Statements, and References Appendix A. Additional Information About the Signature A. Additional Information About the Signature B. K-SIF and SIF Algorithms B. K-SIF and SIF Algorithms C. Additional Numerical Experiments C. Additional Numerical Experiments 4.1. Parameters Sensitivity Analysis We investigate the behavior of K-SIF and SIF with respect to their two main parameters: the depth of the signature k and the number of split windows ω. For the sake of place, the experiment on the depth is postponed in Section C.1 in the Appendix. The Role of the Signature Split Window. The number of split windows allows the extraction of information over specific intervals (randomly selected) of the underlying data. Thus, at each tree node, the focus will be on a particular portion of the data, which is the same across all the sample curves for comparison purposes. This approach ensures that the analysis is performed on comparable sections of the data, providing a systematic way to examine and compare different intervals or features across the sample curves. The Role of the Signature Split Window. We explore the role of this parameter with two different datasets that reproduce two types of anomaly scenarios. The first considers isolated anomalies in a small interval, while the second contains persistent ones across all the function parametrization. In this way, we observe the behavior of K-SIF and SIF with respect to different types of anomalies. The first dataset is constructed as follows. We simulate 100 constant functions. We then select at random 90% of these curves and Gaussian noise on a sub-interval; for the remaining 10% of the curves, we add Gaussian noise on another sub-interval, different from the first one. More precisely: • 90% of the curves, considered as normal, are generated according to with ε(t) ∼ N (0, 1), b ∼ U([0, 100]) and U representing the uniform distribution. • 10% of the curves, considered as abnormal, are generated according to where ε(t) ∼ N (0, 1) and b ∼ U([0, 100]). We simulate at random 90% of the paths with µ = 0, σ = 0.5, and consider them as normal data. Then, the remaining 10% are simulated with drift µ = 0.2, standard deviation σ = 0.4, and considered abnormal data. We compute K-SIF with different numbers of split windows, varying from 1 to 10, with a truncation level set equal to 2 and N = 1, 000 the number of trees. The experiment is repeated 100 times, and we report the averaged AUC under the ROC curves in Figure 1 for both datasets and three pre-selected dictionaries. For the first dataset, where anomalies manifest in a small portion of the functions, increasing the number of splits significantly enhances the algorithm’s performance in detecting anomalies. The performance improvement shows a plateau after nine split windows. In the case of the second dataset with persistent anomalies, a higher number of split windows has a marginal impact on the algorithm’s performance, maintaining satisfactory results. Therefore, without prior knowledge about the data, opting for a relatively high number of split windows, such as 10, would ensure robust performance in both scenarios. Additionally, a more significant number of split windows enables the computation of the signature on a smaller portion of the functions, leading to improved computational efficiency. This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Decoding Split Window Sensitivity in Signature Isolation Forests

Afkodning af delt vinduesfølsomhed i signaturisolationsskove

Dekodierung der Split-Window-Empfindlichkeit in Signaturisolationswäldern

Descifrando la sensibilidad de la ventana dividida en bosques de aislamiento de firmas

Az osztott ablak érzékenységének dekódolása a Signature Isolation Forestsben

Decodifica della sensibilità della finestra divisa nelle foreste di isolamento delle firme

署名分離フォレストにおける分割ウィンドウの感度のデコード

Decoding Split Window Sensitivity ka Dithokgweng tša go Ikarola tša Mosaeno

Декодирование чувствительности разделенного окна в лесах изоляции сигнатур

Decoding Gutandukanya Idirishya Sensitivity mumashyamba yo kwigunga

Kusimbua Unyeti wa Dirisha la Kugawanyika katika Misitu ya Kutengwa kwa Sahihi

دستخطی تنہائی کے جنگلات میں اسپلٹ ونڈو کی حساسیت کو ڈی کوڈنگ کرنا

Ukuqonda Ukwahlulwa Kwefestile Yeefestile KuMsayino Wokwahlulwa Kwamahlathi

Stream Processing - Windows

Everyone tends to remove external devices such as USB drives or external disk drives without using the safe removal option on a Windows PC. However, this practice can harm your device in the long run. This is because your operating system constantly communicates with connected external drives to retrieve information. Even if you close all folders related to the external disk, it is still highly recommended to use the “Safely Remove Hardware” option when ejecting your device. If you’re unfamiliar with the steps, in this article, I will guide you through multiple methods to safely and properly eject USB drives or external disk drives from your Windows 11 PC. While this guide focuses on external SSDs, the same methods can also be used for external HDDs and USB drives. So, even though I’ll be referring to an external SSD, keep in mind that these steps are applicable to any external disk drive or USB device. My connected SSD to my PC is named Expansion. Method 1: The Generic Way to Eject USB or Disk Drive From Taskbar: Once you connect the SSD or USB to your device, to eject it from your pc, you need to click the Show Hidden Items in the right corner of your taskbar. Now, the popup option to eject the external device will appear. From this, you need to select the option named “Eject [Device Name]” for the connected external device. Note: If you have multiple external devices connected, the list will show all the connected devices. In this case, you should carefully choose the “Eject [Device Name]” for the specific external disk drive you want to eject. In this way, you can safely eject any external disk drives connected to your Windows 11 PC. You will get a popup message that says “Your device is safe to remove.” If you receive an error message saying “Problem Ejecting USB Attached SCSI (UAS) Mass Storage Device”, don’t worry. This is a common error message, but to fix it, simply follow the steps provided below. The Fix for Problem Ejecting USB Attached SCSI (UAS) Mass Storage Devices: I have tried and tested the fixes listed below, and I’ve arranged them according to the level of difficulty in implementing each one. It’s recommended to back up your external device if necessary before attempting any of these fixes. Fix 1: Using Task Manager: The main cause of this error is usually not closing the external device’s folder or having some files from the external device open or running in the background. Additionally, you should check if OneDrive or Google Drive is backing up files from your external disk drive in the background. This can be identified by checking the Task Manager. Open the Task Manager using the keyboard shortcut CTRL + SHIFT + ESC. Look for any processes running in the background. If you find any, I recommend ending the process. Next, search for the File Explorer process in the Task Manager. Once you locate it, right-click on it and select the Restart option. This will restart the File Explorer process, which will close all folders related to the external disk drives. After this, you can use the generic method mentioned earlier to safely remove the external device, and you should no longer encounter this error when removing it from your PC. Method 2: Eject External Disk Drives Using Windows Settings: If you want to try something different from the generic method, Windows 11 offers an option to remove connected external devices through Windows Settings. To learn how to do this, follow the instructions below. Use the keyboard shortcut Winkey + I to launch Windows Settings. Then, go to the Bluetooth & Devices section. Alternatively, you can directly access the Bluetooth & Devices options from the Device Ejection Menu. In the list of options, choose Devices. This will display all the connected external devices on your PC, such as a USB mouse, USB disk drive, USB SSD disk drive, and many more. Now, you can see the 3 horizontal dots (…) at the end of the connected external device, and select the Remove device option. This option will instantly remove the connected external device from your Windows 11 PC. After doing this, you can directly remove or unplug the USB disk drive from your PC, and it won’t affect both of your devices. Method 3: Eject External USB or Disk Drives From the Device Manager: You can use this method if your external devices become corrupted and Windows is unable to safely remove the external devices connected to your PC. Open the Device Manager window using the keyboard shortcut: Winkey + X & choose the Device Manager from the list. Open Device Manager from Winkey + X Shortcut Now, you need to expand the Disk Drives option from the list to view all the connected external disk drives.


Choose the connected external device; in my case, the device name is “Seagate Expansion SCSI Disk Device“ Expanding Disk Drive options from Device Manager Then, you need to right-click on the device name and choose the option Uninstall Device.


A prompt will appear on your screen, asking you to uninstall the connected external device, as shown in the gif below. Now, you can unplug the connected external devices. Take Away: By following the steps, you can ensure that your external SSD, HDD, or USB drive is safely removed from your Windows 11 PC without causing any potential damage. Whether you’re using the generic method or Windows Settings, it’s essential to properly eject your external devices to avoid errors or data corruption. Always remember to use the “Safely Remove Hardware” option for long-term protection of your external drives and data. Everyone tends to remove external devices such as USB drives or external disk drives without using the safe removal option on a Windows PC. However, this practice can harm your device in the long run . This is because your operating system constantly communicates with connected external drives to retrieve information. Even if you close all folders related to the external disk, it is still highly recommended to use the “Safely Remove Hardware” option when ejecting your device. USB drives external disk drives this practice can harm your device in the long run operating system constantly communicates highly recommended to use the “Safely Remove Hardware” option If you’re unfamiliar with the steps, in this article, I will guide you through multiple methods to safely and properly eject USB drives or external disk drives from your Windows 11 PC. multiple methods to safely and properly eject USB drives While this guide focuses on external SSDs, the same methods can also be used for external HDDs and USB drives . So, even though I’ll be referring to an external SSD, keep in mind that these steps are applicable to any external disk drive or USB device . My connected SSD to my PC is named Expansion . the same methods can also be used for external HDDs and USB drives any external disk drive USB device Expansion Method 1: The Generic Way to Eject USB or Disk Drive From Taskbar: Once you connect the SSD or USB to your device, to eject it from your pc, you need to click the Show Hidden Items in the right corner of your taskbar. Once you connect the SSD or USB to your device, to eject it from your pc, you need to click the Show Hidden Items in the right corner of your taskbar. Show Hidden Items Now, the popup option to eject the external device will appear. From this, you need to select the option named “Eject [Device Name]” for the connected external device. Now, the popup option to eject the external device will appear. From this, you need to select the option named “Eject [Device Name]” for the connected external device. popup option to eject the external device “Eject [Device Name]” Note: If you have multiple external devices connected, the list will show all the connected devices. In this case, you should carefully choose the “Eject [Device Name]” for the specific external disk drive you want to eject. Note: If you have multiple external devices connected , the list will show all the connected devices. In this case, you should carefully choose the “Eject [Device Name]” for the specific external disk drive you want to eject. Note: multiple external devices connected “Eject [Device Name]” In this way, you can safely eject any external disk drives connected to your Windows 11 PC. You will get a popup message that says “Your device is safe to remove.” If you receive an error message saying “Problem Ejecting USB Attached SCSI (UAS) Mass Storage Device” , don’t worry. This is a common error message , but to fix it, simply follow the steps provided below. “Problem Ejecting USB Attached SCSI (UAS) Mass Storage Device” common error message The Fix for Problem Ejecting USB Attached SCSI (UAS) Mass Storage Devices: I have tried and tested the fixes listed below, and I’ve arranged them according to the level of difficulty in implementing each one. It’s recommended to back up your external device if necessary before attempting any of these fixes. tried and tested the fixes level of difficulty It’s recommended to back up your external device Fix 1: Using Task Manager: The main cause of this error is usually not closing the external device’s folder or having some files from the external device open or running in the background . Additionally, you should check if OneDrive or Google Drive is backing up files from your external disk drive in the background. This can be identified by checking the Task Manager . main cause of this error open or running in the background OneDrive Google Drive backing up files from your external disk drive Task Manager Open the Task Manager using the keyboard shortcut CTRL + SHIFT + ESC. Open the Task Manager using the keyboard shortcut CTRL + SHIFT + ESC. Look for any processes running in the background. If you find any, I recommend ending the process. Look for any processes running in the background. If you find any, I recommend ending the process . I recommend ending the process Next, search for the File Explorer process in the Task Manager. Once you locate it, right-click on it and select the Restart option. Next, search for the File Explorer process in the Task Manager. Once you locate it, right-click on it and select the Restart option. File Explorer process right-click on it Restart This will restart the File Explorer process, which will close all folders related to the external disk drives. This will restart the File Explorer process , which will close all folders related to the external disk drives. restart the File Explorer process After this, you can use the generic method mentioned earlier to safely remove the external device, and you should no longer encounter this error when removing it from your PC. After this, you can use the generic method mentioned earlier to safely remove the external device, and you should no longer encounter this error when removing it from your PC. generic method should no longer encounter this error Method 2: Eject External Disk Drives Using Windows Settings: If you want to try something different from the generic method, Windows 11 offers an option to remove connected external devices through Windows Settings . To learn how to do this, follow the instructions below. Windows 11 offers an option to remove connected external devices through Windows Settings Use the keyboard shortcut Winkey + I to launch Windows Settings. Then, go to the Bluetooth & Devices section. Use the keyboard shortcut Winkey + I to launch Windows Settings . Then, go to the Bluetooth & Devices section. keyboard shortcut Windows Settings Bluetooth & Devices Alternatively, you can directly access the Bluetooth & Devices options from the Device Ejection Menu. Alternatively, you can directly access the Bluetooth & Devices options from the Device Ejection Menu . Bluetooth & Devices Device Ejection Menu In the list of options, choose Devices. This will display all the connected external devices on your PC, such as a USB mouse, USB disk drive, USB SSD disk drive, and many more. In the list of options, choose Devices . This will display all the connected external devices on your PC, such as a USB mouse , USB disk drive , USB SSD disk drive , and many more. Devices connected external devices USB mouse USB disk drive USB SSD disk drive Now, you can see the 3 horizontal dots (…) at the end of the connected external device, and select the Remove device option. Now, you can see the 3 horizontal dots (…) at the end of the connected external device, and select the Remove device option. Remove device This option will instantly remove the connected external device from your Windows 11 PC. This option will instantly remove the connected external device from your Windows 11 PC. After doing this, you can directly remove or unplug the USB disk drive from your PC, and it won’t affect both of your devices. Method 3: Eject External USB or Disk Drives From the Device Manager: You can use this method if your external devices become corrupted and Windows is unable to safely remove the external devices connected to your PC. external devices become corrupted Windows is unable to safely remove the external devices Open the Device Manager window using the keyboard shortcut: Winkey + X & choose the Device Manager from the list. Open the Device Manager window using the keyboard shortcut: Winkey + X & choose the Device Manager from the list. Device Manager window Open Device Manager from Winkey + X Shortcut Now, you need to expand the Disk Drives option from the list to view all the connected external disk drives. Choose the connected external device; in my case, the device name is “Seagate Expansion SCSI Disk Device“ Now, you need to expand the Disk Drives option from the list to view all the connected external disk drives. Now, you need to expand the Disk Drives option from the list to view all the connected external disk drives . expand the Disk Drives option connected external disk drives Choose the connected external device; in my case, the device name is “Seagate Expansion SCSI Disk Device“ Choose the connected external device; in my case, the device name is “ Seagate Expansion SCSI Disk Device “ Seagate Expansion SCSI Disk Device Expanding Disk Drive options from Device Manager Then, you need to right-click on the device name and choose the option Uninstall Device. A prompt will appear on your screen, asking you to uninstall the connected external device, as shown in the gif below. Then, you need to right-click on the device name and choose the option Uninstall Device. Then, you need to right-click on the device name and choose the option Uninstall Device . Uninstall Device A prompt will appear on your screen, asking you to uninstall the connected external device, as shown in the gif below. A prompt will appear on your screen, asking you to uninstall the connected external device , as shown in the gif below. prompt will appear uninstall the connected external device Now, you can unplug the connected external devices. Now, you can unplug the connected external devices. Take Away: By following the steps, you can ensure that your external SSD , HDD , or USB drive is safely removed from your Windows 11 PC without causing any potential damage. Whether you’re using the generic method or Windows Settings , it’s essential to properly eject your external devices to avoid errors or data corruption. external SSD HDD USB drive generic method Windows Settings Always remember to use the “Safely Remove Hardware” option for long-term protection of your external drives and data. Always remember “Safely Remove Hardware” option

How to Eject a USB or External SSD/HDD in Windows 11?

On October 16, 2024, the Node.js community reached a significant milestone with the release of Node.js v23.0.0. This latest version introduces several improvements and new features, but it also brings an important change: Node.js will no longer support 32-bit Windows. Why Drop 32-bit Windows Support? According to a GitHub issue, only 0.27% of users are running Windows on 32-bit machines. Moreover, Node.js had already stopped supporting 32-bit Linux due to toolchain limitations and previously dropped support for Windows 7. Given these factors, maintaining support for 32-bit Windows no longer made sense for the project. What This Means for Users For most Node.js users, this change will have little to no effect. However, if you're still using a 32-bit version of Windows, this update means that Node.js v23.0.0 and all future versions will no longer be compatible with your system. You will need to either upgrade to a 64-bit version of Windows or continue using an older Node.js version that supports 32-bit systems. New Features in Node.js v23.0.0 Aside from this significant change, Node.js v23.0.0 also brings some noteworthy new features, including: Native ES Module Loading with require() A long-requested feature is now available! In previous versions, loading native ES modules (.mjs files) via require() was only possible using the --experimental-require-module flag. With Node.js v23.0.0, this feature is now fully supported without the need for any flags. Here’s a simple example of how you can now load an ES module using require()in Node.js v23.0.0: // Importing a native ES module using require
const { add, subtract } = require('./math.mjs');

// Use the imported functions
console.log(add(5, 3));       // Outputs: 8
console.log(subtract(10, 4)); // Outputs: 6 In this example, we are importing two functions (add and subtract) from an ES module file (math.mjs) using the require() method, which was not natively possible before this release. With these improvements, Node.js continues to evolve as a powerful, modern, and developer-friendly platform. Whether you’re building large-scale applications or working on small projects, Node.js v23.0.0 offers new capabilities that can enhance your development workflow. Note: If you're still on a 32-bit system, consider upgrading soon to take advantage of these new features and improvements! On October 16, 2024 , the Node.js community reached a significant milestone with the release of Node.js v23.0.0 . This latest version introduces several improvements and new features, but it also brings an important change: Node.js will no longer support 32-bit Windows . October 16, 2024 Node.js v23.0.0 Node.js will no longer support 32-bit Windows Why Drop 32-bit Windows Support? According to a GitHub issue , only 0.27% of users are running Windows on 32-bit machines. Moreover, Node.js had already stopped supporting 32-bit Linux due to toolchain limitations and previously dropped support for Windows 7. Given these factors, maintaining support for 32-bit Windows no longer made sense for the project. GitHub issue GitHub issue 0.27% What This Means for Users For most Node.js users, this change will have little to no effect. However, if you're still using a 32-bit version of Windows, this update means that Node.js v23.0.0 and all future versions will no longer be compatible with your system. You will need to either upgrade to a 64-bit version of Windows or continue using an older Node.js version that supports 32-bit systems. Node.js v23.0.0 and all future versions will no longer be compatible New Features in Node.js v23.0.0 Aside from this significant change, Node.js v23.0.0 also brings some noteworthy new features, including: Native ES Module Loading with require() require() A long-requested feature is now available! In previous versions, loading native ES modules ( .mjs files) via require() was only possible using the --experimental-require-module flag. With Node.js v23.0.0, this feature is now fully supported without the need for any flags. .mjs require() --experimental-require-module Here’s a simple example of how you can now load an ES module using require() in Node.js v23.0.0: require() // Importing a native ES module using require
const { add, subtract } = require('./math.mjs');

// Use the imported functions
console.log(add(5, 3));       // Outputs: 8
console.log(subtract(10, 4)); // Outputs: 6 // Importing a native ES module using require
const { add, subtract } = require('./math.mjs');

// Use the imported functions
console.log(add(5, 3));       // Outputs: 8
console.log(subtract(10, 4)); // Outputs: 6 In this example, we are importing two functions ( add and subtract ) from an ES module file ( math.mjs ) using the require() method, which was not natively possible before this release. add subtract math.mjs require() With these improvements, Node.js continues to evolve as a powerful, modern, and developer-friendly platform. Whether you’re building large-scale applications or working on small projects, Node.js v23.0.0 offers new capabilities that can enhance your development workflow. Note: If you're still on a 32-bit system, consider upgrading soon to take advantage of these new features and improvements! Note:

Node.js v23.0.0 Released: The End of 32-bit Windows Support

Authors:
(1) Dorian W. P. Amaral, Department of Physics and Astronomy, Rice University and These authors contributed approximately equally to this work;
(2) Mudit Jain, Department of Physics and Astronomy, Rice University, Theoretical Particle Physics and Cosmology, King’s College London and These authors contributed approximately equally to this work;
(3) Mustafa A. Amin, Department of Physics and Astronomy, Rice University;
(4) Christopher Tunnell, Department of Physics and Astronomy, Rice University. Table of Links Abstract and 1 Introduction 2 Calculating the Stochastic Wave Vector Dark Matter Signal 2.1 The Dark Photon Field 2.2 The Detector Signal 3 Statistical Analysis and 3.1 Signal Likelihood 3.2 Projected Exclusions 4 Application to Accelerometer Studies 4.1 Recasting Generalised Limits onto B − L Dark Matter 5 Future Directions 6 Conclusions, Acknowledgments, and References A Equipartition between Longitudinal and Transverse Modes B Derivation of Marginal Likelihood with Stochastic Field Amplitude C Covariance Matrix D The Case of the Gradient of a Scalar 5 Future Directions 5.1 Longer Observation Times 5.2 Expanding the Mass Window This paper is available on arxiv under CC BY 4.0 DEED license. Authors: (1) Dorian W. P. Amaral, Department of Physics and Astronomy, Rice University and These authors contributed approximately equally to this work; (2) Mudit Jain, Department of Physics and Astronomy, Rice University, Theoretical Particle Physics and Cosmology, King’s College London and These authors contributed approximately equally to this work; (3) Mustafa A. Amin, Department of Physics and Astronomy, Rice University; (4) Christopher Tunnell, Department of Physics and Astronomy, Rice University. Authors: Authors: (1) Dorian W. P. Amaral, Department of Physics and Astronomy, Rice University and These authors contributed approximately equally to this work; (2) Mudit Jain, Department of Physics and Astronomy, Rice University, Theoretical Particle Physics and Cosmology, King’s College London and These authors contributed approximately equally to this work; (3) Mustafa A. Amin, Department of Physics and Astronomy, Rice University; (4) Christopher Tunnell, Department of Physics and Astronomy, Rice University. Table of Links Abstract and 1 Introduction Abstract and 1 Introduction 2 Calculating the Stochastic Wave Vector Dark Matter Signal 2.1 The Dark Photon Field 2.1 The Dark Photon Field 2.2 The Detector Signal 2.2 The Detector Signal 3 Statistical Analysis and 3.1 Signal Likelihood 3 Statistical Analysis and 3.1 Signal Likelihood 3.2 Projected Exclusions 3.2 Projected Exclusions 4 Application to Accelerometer Studies 4 Application to Accelerometer Studies 4.1 Recasting Generalised Limits onto B − L Dark Matter 4.1 Recasting Generalised Limits onto B − L Dark Matter 5 Future Directions 5 Future Directions 6 Conclusions, Acknowledgments, and References 6 Conclusions, Acknowledgments, and References A Equipartition between Longitudinal and Transverse Modes A Equipartition between Longitudinal and Transverse Modes B Derivation of Marginal Likelihood with Stochastic Field Amplitude B Derivation of Marginal Likelihood with Stochastic Field Amplitude C Covariance Matrix C Covariance Matrix D The Case of the Gradient of a Scalar D The Case of the Gradient of a Scalar 5 Future Directions 5.1 Longer Observation Times 5.2 Expanding the Mass Window This paper is available on arxiv under CC BY 4.0 DEED license. This paper is available on arxiv under CC BY 4.0 DEED license. available on arxiv

Longer Observation Times and Expanding the Mass Window

Background DevOps teams face numerous challenges during the modernization of CI/CD build systems. One such challenge arises when teams continue to build Windows-based applications that require older versions of Windows. In these cases, a Windows Server 2019 Update 2004/20H2 container can be used to help the team build these applications without needing many code changes. Since AWS does not provide an AMI for Windows Server 2019 Update 2004/20H2, we must create one manually so that it can be used to create nodes in the EKS cluster, which can then be integrated into the CI/CD pipeline. Below are the steps to generate a custom image for Windows Server 2019 Update 2004/20H2. In this guide, we will generate the image for Kubernetes v1.27. Prerequisites: AWS Account
An IAM user with administrative permissions or a user with full permissions for EC2 and AMI management Navigate to the Right Service in AWS & Create Windows Server 2019 Update 2004/20H2 AMI: Log in to the AWS account where you want to create the AMI, using a user with the necessary permissions to create AMIs. Once logged in, search for the Image Builder service, click on EC2 Image Builder, and start by clicking Create Image Pipeline. Step 1: Define the name and description of the AMI, and add tags that will be associated with it. Note: Using tags has many advantages, including better management, organization, and automation. Step 2: Choose the recipe for the AMI. You will have two options: Use Existing Recipe or Create New Recipe. If you already have a recipe with the desired configuration, select Use Existing Recipe. For this documentation, we will proceed with Create New Recipe since we are assuming that no existing recipe is available. Selecting Create New Recipe opens up several additional options to configure: Selecting Image Type (What type of image output is required):
1. Amazon Machine Image (AMI).

2. Docker Image 



Name and Description for this configuration


Base Image:
1. Image  

2. Image OS  

3. Image Origin 

4. Image Name (populated based on the previous selections) 



Instance Configuration


Working Directory (can be left as default)


Components:
1. Step 1: Choose build components to produce the desired AMI  

2. Step 2: (Optional) Select tests to verify the output AMI (post-build) Now that we have defined all the options, let's go through them one by one. After selecting Create New Recipe, we need to choose the output type we are trying to achieve from this Image Builder — whether it’s an AMI or a Docker image. Since we need a Windows AMI for the EKS node, let's select Amazon Machine Image (AMI). Let's use the same name and description for the AMI that we defined in Step 1, as we are working within the same image builder pipeline. Now it's time to select the Base Image in the "Select Image" step. The first step is to decide what type of Base Image we need. There are four available options—let's review each one and when to choose them, so we can determine which is best for our needs. Select managed images: Choose this option if you need a stable, secure, and up-to-date base image managed by AWS or your team.
AWS Marketplace images: Choose this option if you need an image with specific software or configurations that is already available in the AWS Marketplace.
Enter custom AMI ID: Choose this option if you already have a custom AMI in your AWS account with specific configurations, applications, or an operating system that you want to use as the base for a new image.
Import base image: Choose this option if you are migrating from a virtual machine (VM) environment to the cloud and want to import a VM image from your existing environment. For this process, we are choosing the “Select Managed Images” option since we need a stable, secure, and up-to-date base image. Selecting this option opens up a few more choices, so let's go through them one by one. Next, we need to select the Operating System. Since we are creating this Image Builder for Windows Server 2019 Update 2004/20H2, let's select Windows OS. Next is the Image Origin stage, where you have three options to choose from: Quick start (Amazon-managed): Select this if you don’t have any images created yet and want to use an Amazon-managed image.
Images owned by me: Select this if you already have an image created using Image Builder.
Images shared with me: Select this if someone has shared an image with you that was created using Image Builder. I am choosing Images owned by me since I already created an image when the EKS cluster was on version 1.23, which supported Windows Server 2004. Note: If you don’t have a pre-existing image of Windows Server 2004, it is best to create an AMI. For more information, refer to this link: Importing a VM as an Image. This way, you can select "Images owned by me" and choose the AMI that you created. For Auto-Versioning select “Use selected OS version” Keep the remaining settings as they are, and move on to the Build components selection. In the search box, search for "eks" and filter with Amazon-Managed. Then, check the component and specify the version (eg: 1.27.0); otherwise, it will build the latest available version. Make sure the "Available" sign turns green before proceeding further. Keep everything else default and Add Tags and click Next. Step 3: The next step is “Define Image Creation Process”. In this, you have 2 options to choose from Default workflows or Custom workflow, we will go with default option “Default workflows” and click Next. Step 4: The next step is "Define infrastructure configuration" Although this step is optional, it is best to either select "Use Existing Infrastructure Configuration" if one is already configured, or choose "Create infrastructure configuration using service defaults" Step 5: The next step is "Create distribution settings" Select "Create distribution settings using service defaults" and click Next. Step 6: The final step is to review all the configurations and click Create Pipeline. This will create the Image Builder pipeline. Once the pipeline is created, it can be used in EKS to create a Windows Server 2019 Update 2004/20H2 node group. Background DevOps teams face numerous challenges during the modernization of CI/CD build systems. One such challenge arises when teams continue to build Windows-based applications that require older versions of Windows. In these cases, a Windows Server 2019 Update 2004/20H2 container can be used to help the team build these applications without needing many code changes. Since AWS does not provide an AMI for Windows Server 2019 Update 2004/20H2, we must create one manually so that it can be used to create nodes in the EKS cluster, which can then be integrated into the CI/CD pipeline. Below are the steps to generate a custom image for Windows Server 2019 Update 2004/20H2. In this guide, we will generate the image for Kubernetes v1.27. Prerequisites: AWS Account An IAM user with administrative permissions or a user with full permissions for EC2 and AMI management AWS Account An IAM user with administrative permissions or a user with full permissions for EC2 and AMI management Navigate to the Right Service in AWS & Create Windows Server 2019 Update 2004/20H2 AMI: Log in to the AWS account where you want to create the AMI, using a user with the necessary permissions to create AMIs. Once logged in, search for the Image Builder service, click on EC2 Image Builder , and start by clicking Create Image Pipeline . EC2 Image Builder Create Image Pipeline Step 1: Define the name and description of the AMI, and add tags that will be associated with it. Step 1: Note: Using tags has many advantages, including better management, organization, and automation. Note: Note: Step 2: Choose the recipe for the AMI. You will have two options: Use Existing Recipe or Create New Recipe . If you already have a recipe with the desired configuration, select Use Existing Recipe. For this documentation, we will proceed with Create New Recipe since we are assuming that no existing recipe is available. Step 2: Use Existing Recipe Create New Recipe Create New Recipe Selecting Create New Recipe opens up several additional options to configure: Create New Recipe Selecting Image Type (What type of image output is required):
1. Amazon Machine Image (AMI).

2. Docker Image Name and Description for this configuration Base Image:
1. Image  

2. Image OS  

3. Image Origin 

4. Image Name (populated based on the previous selections) Instance Configuration Working Directory (can be left as default) Components:
1. Step 1: Choose build components to produce the desired AMI  

2. Step 2: (Optional) Select tests to verify the output AMI (post-build) Selecting Image Type (What type of image output is required): 1. Amazon Machine Image (AMI).

2. Docker Image Selecting Image Type (What type of image output is required): Selecting Image Type 1. Amazon Machine Image (AMI).

2. Docker Image 1. Amazon Machine Image (AMI).

2. Docker Image Name and Description for this configuration Name and Description for this configuration Name and Description Base Image: 1. Image  

2. Image OS  

3. Image Origin 

4. Image Name (populated based on the previous selections) Base Image: Base Image: 1. Image  

2. Image OS  

3. Image Origin 

4. Image Name (populated based on the previous selections) 1. Image  

2. Image OS  

3. Image Origin 

4. Image Name (populated based on the previous selections) Instance Configuration Instance Configuration Instance Configuration Working Directory (can be left as default) Working Directory (can be left as default) Working Directory Components: 1. Step 1: Choose build components to produce the desired AMI  

2. Step 2: (Optional) Select tests to verify the output AMI (post-build) Components: Components: 1. Step 1: Choose build components to produce the desired AMI  

2. Step 2: (Optional) Select tests to verify the output AMI (post-build) 1. Step 1: Choose build components to produce the desired AMI  

2. Step 2: (Optional) Select tests to verify the output AMI (post-build) Now that we have defined all the options, let's go through them one by one. After selecting Create New Recipe, we need to choose the output type we are trying to achieve from this Image Builder — whether it’s an AMI or a Docker image. Since we need a Windows AMI for the EKS node, let's select Amazon Machine Image (AMI). Let's use the same name and description for the AMI that we defined in Step 1, as we are working within the same image builder pipeline. Now it's time to select the Base Image in the " Select Image " step. The first step is to decide what type of Base Image we need. There are four available options—let's review each one and when to choose them, so we can determine which is best for our needs. Select Image Select managed images: Choose this option if you need a stable, secure, and up-to-date base image managed by AWS or your team. AWS Marketplace images: Choose this option if you need an image with specific software or configurations that is already available in the AWS Marketplace. Enter custom AMI ID: Choose this option if you already have a custom AMI in your AWS account with specific configurations, applications, or an operating system that you want to use as the base for a new image. Import base image: Choose this option if you are migrating from a virtual machine (VM) environment to the cloud and want to import a VM image from your existing environment. Select managed images: Choose this option if you need a stable, secure, and up-to-date base image managed by AWS or your team. Select managed images: AWS Marketplace images: Choose this option if you need an image with specific software or configurations that is already available in the AWS Marketplace. AWS Marketplace images: Enter custom AMI ID: Choose this option if you already have a custom AMI in your AWS account with specific configurations, applications, or an operating system that you want to use as the base for a new image. Enter custom AMI ID: Import base image: Choose this option if you are migrating from a virtual machine (VM) environment to the cloud and want to import a VM image from your existing environment. Import base image: For this process, we are choosing the “ Select Managed Images ” option since we need a stable, secure, and up-to-date base image. Selecting this option opens up a few more choices, so let's go through them one by one. Select Managed Images Next, we need to select the Operating System. Since we are creating this Image Builder for Windows Server 2019 Update 2004/20H2, let's select Windows OS. Next is the Image Origin stage, where you have three options to choose from: Image Origin Quick start (Amazon-managed): Select this if you don’t have any images created yet and want to use an Amazon-managed image. Images owned by me: Select this if you already have an image created using Image Builder. Images shared with me: Select this if someone has shared an image with you that was created using Image Builder. Quick start (Amazon-managed): Select this if you don’t have any images created yet and want to use an Amazon-managed image. Quick start (Amazon-managed): Images owned by me: Select this if you already have an image created using Image Builder. Images owned by me: Images shared with me: Select this if someone has shared an image with you that was created using Image Builder. Images shared with me: I am choosing Images owned by me since I already created an image when the EKS cluster was on version 1.23, which supported Windows Server 2004. Images owned by me Note: If you don’t have a pre-existing image of Windows Server 2004, it is best to create an AMI. For more information, refer to this link: Importing a VM as an Image . This way, you can select " Images owned by me " and choose the AMI that you created. Note: Note: Importing a VM as an Image Importing a VM as an Image Images owned by me For Auto-Versioning select “ Use selected OS version ” Use selected OS version Keep the remaining settings as they are, and move on to the Build components selection. In the search box, search for " eks " and filter with Amazon-Managed . Then, check the component and specify the version (eg: 1.27.0) ; otherwise, it will build the latest available version. Make sure the " Available " sign turns green before proceeding further. eks Amazon-Managed version (eg: 1.27.0) Available Keep everything else default and Add Tags and click Next . Next Step 3: The next step is “ Define Image Creation Process” . In this, you have 2 options to choose from Default workflows or Custom workflow , we will go with default option “ Default workflows” and click Next. Step 3: Define Image Creation Process” Default workflows Custom workflow Default workflows” Next. Step 4: The next step is " Define infrastructure configuration " Although this step is optional, it is best to either select " Use Existing Infrastructure Configuration " if one is already configured, or choose " Create infrastructure configuration using service defaults " Step 4: Define infrastructure configuration Use Existing Infrastructure Configuration Create infrastructure configuration using service defaults Step 5: The next step is " Create distribution settings " Select " Create distribution settings using service defaults " and click Next . Step 5: Create distribution settings Create distribution settings using service defaults Next Step 6: The final step is to review all the configurations and click Create Pipeline. Step 6: Create Pipeline. This will create the Image Builder pipeline. Once the pipeline is created, it can be used in EKS to create a Windows Server 2019 Update 2004/20H2 node group.

How to Generate EKS Worker Node Image - Windows 2019 Update 2004/20H2

Exploring "Clarity Windows" in AI: The Unpredictable Moments of Perceived Consciousness

Εξερευνώντας τα "Clarity Windows" στο AI: Οι απρόβλεπτες στιγμές της αντιληπτής συνείδησης

Explorando las "ventanas de claridad" en la IA: los momentos impredecibles de la conciencia percibida

AI-n "Argitasun-leihoak" arakatzea: hautematen den kontzientziaren une ezustekoak

Exploration des « fenêtres de clarté » en IA : les moments imprévisibles de la conscience perçue

Istraživanje "prozora jasnoće" u umjetnoj inteligenciji: nepredvidivi trenuci percipirane svijesti

AI における「明瞭性の窓」を探る: 知覚された意識の予測不可能な瞬間

Истражување на „Clarity Windows“ во вештачката интелигенција: непредвидливите моменти на перцепирана свест

په AI کې د "وضاحت وینډوز" سپړنه: د پوه شوي شعور غیر متوقع شیبې

AI nisqapi "Clarity Windows" nisqamanta maskay: Conciencia Percibida nisqamanta mana yachay atina pachakuna

Eksplorimi i "Dritareve të qartësisë" në AI: Momentet e paparashikueshme të ndërgjegjes së perceptuar

Истраживање „прозора јасноће“ у АИ: непредвидиви тренуци перципиране свести

AI இல் "தெளிவு விண்டோஸ்" ஆய்வு: உணரப்பட்ட நனவின் கணிக்க முடியாத தருணங்கள்

Anchor the framework for Solana development, currently lacks support for Windows systems. Hence, a Linux environment is required for compatibility with Solana tools and technologies. This article will guide you through installing Windows Subsystem for Linux (WSL) and other necessary dependencies and technologies, such as Rust, Solana CLI, Node.js, and Yarn, required for Solana development on your Windows system. Prerequisites Windows 10+Good Internet connectionSolana enthusiast Installations You will install Windows Subsystem for Linus (WSL), Rust and Cargo, Solana CLI, Node.js, Yarn, and Vs code. 1) Install Windows Subsystem for Linus (WSL) WSL will allow you to run a Linux environment directly on your Windows system. Open your Powershell in administrator mode and run this command. wsl --install The default wsl distribution, ubuntu, will be installed. Once installation is complete, restart your machine. Confirm your WSL version and distribution. wsl -l -v You should see this: Set up your Linux distribution username and password Go to the search menu on your computer, type Ubuntu, then open it.
You’ll be required to create a username and password. Follow the instructions to do so. Be sure to save your password somewhere else. If you run into installation errors or want to install another distribution other than Ubuntu, check WSL's complete installation guide 2) Install Rust and Cargo Rust is the language for writing Solana programs. Cargo is a Rust package manager for managing dependencies, building, testing, and deploying Rust codes. To install Rust and Cargo, run this command on your Ubuntu curl - proto '=https' - tlsv1.2 -sSf https://sh.rustup.rs | sh Then, Press 1 or enter to complete the installation Once installation is complete, confirm your Rust and Cargo version with the following commands rustc --version

cargo --version 3) Install Solana Cl To install Solana, run this command on your Ubuntu sh -c "$(curl -sSfL https://release.solana.com/stable/install)" After the installation is complete, confirm the Solana version using this command solana --version Create your Solana wallet and generate your keypairs. Create a default Solana wallet, generate your keypairs, and request free devnet tokens for your wallet. To create your Solana wallet use this command solana-keygen new create a passphrase Ensure to save your public key(a.k.a wallet address) and passphrase(highlighted below in yellow) in a secure location.Your private key is stored locally on your PC. Request for devnets to deploy your Solana programs. To get 10 Solana devnet tokens for your wallet, run this command Solana airdrop 10 This will send devnet to the default wallet you just created.To send to a different wallet, useSolana airdrop 10 <wallet address> 4) Install node.js If you’ve previously installed Node.js on your Windows, you should consider installing Node.js again specifically within your WSL to ensure compatibility. To Install Node.js using Node Version Manager (NVM) Run this nvm command on your Ubuntu curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash confirm NVM installation command -v nvm you should see this Otherwise, close and reopen your Ubuntu and rerun the command. Install the stable LTS version of Node Js with this command nvm install - lts Confirm the installations of Node.js and npm versions node --version
npm --version 5) Install yarn yarn official documentation highlighted corepackas one of the two preferred methods of installing Yarn.npm yarn global installation is not recommended. To install yarn, enable core pack and initialize a yarn project using the following commands npm install -g corepack
corepack enable
yarn init 6) Install VS Code Download VScode directly from the official website To enable support for the WSL environment in your VSCode, install the WSL extension. To do so, open VScode, click on the marketplace or “Ctrl + shift + x “, then search for and install the Remote — WSL Extension. Additionally, install the ‘rust-analyzer’ extension for Rust language support. 7) Install Anchor Anchor is the Solana framework for writing secure Solana programs. Install Anchor using Anchor Version Manager (AVM) with this command cargo install - git https://github.com/coral-xyz/anchor avm - locked - force Install the latest Anchor version and set it as the default, using the following commands: avm install latest
avm use latest Confirm Anchor installation Anchor –version If you encounter any installation error check Anchor's official docs Congratulations 🥳 you are all set to develop on Solana Blockchain Anchor the framework for Solana development, currently lacks support for Windows systems. Hence, a Linux environment is required for compatibility with Solana tools and technologies. This article will guide you through installing Windows Subsystem for Linux (WSL) and other necessary dependencies and technologies, such as Rust , Solana CLI, Node.js , and Yarn, required for Solana development on your Windows system. Linux Rust Solana Node.js Prerequisites Windows 10+ Good Internet connection Solana enthusiast Installations You will install Windows Subsystem for Linus (WSL), Rust and Cargo, Solana CLI, Node.js, Yarn, and Vs code. 1) Install Windows Subsystem for Linus (WSL) WSL will allow you to run a Linux environment directly on your Windows system. Open your Powershell in administrator mode and run this command. administrator mode administrator mode wsl --install wsl --install The default wsl distribution, ubuntu, will be installed. Once installation is complete, restart your machine. Confirm your WSL version and distribution. wsl -l -v wsl -l -v You should see this: Set up your Linux distribution username and password Set up your Linux distribution username and password Go to the search menu on your computer, type Ubuntu, then open it. You’ll be required to create a username and password. Follow the instructions to do so. Go to the search menu on your computer, type Ubuntu , then open it. Ubuntu You’ll be required to create a username and password. Follow the instructions to do so. Be sure to save your password somewhere else. If you run into installation errors or want to install another distribution other than Ubuntu, check WSL's complete installation guide If you run into installation errors or want to install another distribution other than Ubuntu, check WSL's complete installation guide errors errors installation guide installation guide 2) Install Rust and Cargo Rust is the language for writing Solana programs. Rust Rust Cargo is a Rust package manager for managing dependencies, building, testing, and deploying Rust codes. To install Rust and Cargo, run this command on your Ubuntu curl - proto '=https' - tlsv1.2 -sSf https://sh.rustup.rs | sh curl - proto '=https' - tlsv1.2 -sSf https://sh.rustup.rs | sh Then, Press 1 or enter to complete the installation Once installation is complete, confirm your Rust and Cargo version with the following commands rustc --version

cargo --version rustc --version

cargo --version 3) Install Solana Cl To install Solana, run this command on your Ubuntu sh -c "$(curl -sSfL https://release.solana.com/stable/install)" sh -c "$(curl -sSfL https://release.solana.com/stable/install)" After the installation is complete, confirm the Solana version using this command solana --version solana --version Create your Solana wallet and generate your keypairs. Create your Solana wallet and generate your keypairs. Create a default Solana wallet, generate your keypairs, and request free devnet tokens for your wallet. To create your Solana wallet use this command solana-keygen new solana-keygen new create a passphrase Ensure to save your public key(a.k.a wallet address ) and passphrase( highlighted below in yellow ) in a secure location. Your private key is stored locally on your PC. wallet address highlighted below in yellow Request for devnets to deploy your Solana programs. Request for devnets to deploy your Solana programs. To get 10 Solana devnet tokens for your wallet, run this command Solana airdrop 10 Solana airdrop 10 This will send devnet to the default wallet you just created. To send to a different wallet, use Solana airdrop 10 <wallet address> Solana airdrop 10 <wallet address> 4) Install node.js If you’ve previously installed Node.js on your Windows, you should consider installing Node.js again specifically within your WSL to ensure compatibility. To Install Node.js using Node Version Manager (NVM) Run this nvm command on your Ubuntu curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/master/install.sh | bash confirm NVM installation command -v nvm command -v nvm you should see this Otherwise, close and reopen your Ubuntu and rerun the command. Install the stable LTS version of Node Js with this command Install the stable LTS version of Node Js with this command nvm install - lts nvm install - lts Confirm the installations of Node.js and npm versions node --version
npm --version node --version
npm --version 5) Install yarn yarn official documentation highlighted corepack as one of the two preferred methods of installing Yarn. npm yarn global installation is not recommended. yarn yarn corepack To install yarn, enable core pack and initialize a yarn project using the following commands npm install -g corepack
corepack enable
yarn init npm install -g corepack
corepack enable
yarn init 6) Install VS Code Download VScode directly from the official website official website official website To enable support for the WSL environment in your VSCode, install the WSL extension. To do so, open VScode, click on the marketplace or “Ctrl + shift + x “, then search for and install the Remote — WSL Extension . Remote — WSL Extension Additionally, install the ‘rust-analyzer’ extension for Rust language support. ‘rust-analyzer’ 7) Install Anchor Anchor is the Solana framework for writing secure Solana programs. Anchor Anchor Install Anchor using Anchor Version Manager (AVM) with this command cargo install - git https://github.com/coral-xyz/anchor avm - locked - force cargo install - git https://github.com/coral-xyz/anchor avm - locked - force Install the latest Anchor version and set it as the default, using the following commands: avm install latest
avm use latest avm install latest
avm use latest Confirm Anchor installation Anchor –version Anchor –version If you encounter any installation error check Anchor's official docs If you encounter any installation error check Anchor's official docs Anchor's official docs Anchor's official docs Congratulations 🥳 you are all set to develop on Solana Blockchain

Step-by-Step Solana Setup on Windows Using WSL

Microsoft WordPad, launched in 1995 as a word processor for basic file editing and formatting, is finally being removed from all editions of Windows, starting with Windows 11, version 24H2, and Windows Server 2025. The exact reason behind this removal is unclear, but Microsoft stated that most of its features, including new ones, have been added to  Notepad, which is more feature-rich than WordPad and allows users to transition seamlessly. However, many users didn’t agree, given the fact that WordPad offers more features than any plain text editor, including support for ODF and RTF file formats without requiring additional installation. Look, there could be many more reasons why users might need the WordPad back, but if the built-in support for ODF and RTF file formats is one reason, then note that you can open and edit these files using Microsoft Word, LibreOffice, or OnlyOffice. Moreover, if there is any other reason you want the original WordPad  back on your Windows 11 and 10 system, then read the entire article to  learn how to install WordPad on Windows 11 and 10 in the right way. How to Install WordPad on Windows 11, 10 Winaero  is a popular website that focuses on providing high-quality free apps,  themes, and tutorials for Windows. It’s a trusted site that has been serving millions of users since 2011. It offers the original WordPad package without any tampering and  supports both 32-bit and 64-bit systems. If you dislike the app after  installation, you can quickly remove it using the uninstaller. I’ve tried and tested it on my Windows 11 system, and to be frank, it  ran just like any other Windows built-in app; to be honest, I kind of  liked it—it gives you a nostalgic, childlike feeling. To quickly install WordPad on Windows 11 and 10, follow these instructions. First, download the WordPad installer for Windows 11 and 10.


Once the download is complete, go to the download folder, extract the compressed file, and double-click the extracted file to open the setup wizard (approve the UAC prompt).


When the setup wizard opens, continue by clicking “Next.“ Next, it displays the default installation location; I recommend not changing it and continuing by clicking “Next.“ Here, it will ask whether to install WordPad for the current user or for all users. If you want to install it only for yourself, select the “For the current user only” option. Otherwise, leave the options unchanged, and continue by clicking “Next.“ Finally, click “Install” to start the WordPad installation. The installation will be completed within 3 to 4 seconds. Once the installation is complete, the final finish window will appear, where you can select the “Run WordPad” option to open WordPad immediately after clicking “Finish.“ You can now enjoy WordPad on your Windows 11 and 10 systems. How to Uninstall WordPad on Windows 11, 10 To uninstall WordPad, from Windows 11 and 10, open “Settings“, go to “Apps“, then “Installed apps“, find “WordPad” in the list, click the three dots next to it, and choose “Uninstall” from the menu. Wrap Up WordPad has been closest to the hearts of most of the Windows users, including myself. It was one of the first or second Windows apps  introduced to me during my childhood. Hearing about its removal left me unaffected, as I have since transitioned to many more advanced editors  over the years. However, while writing this article, I installed and used WordPad for a while, which sparked nostalgic memories from my childhood and created a heartwarming feeling. If you’re a WordPad enthusiast, I hope you found this article useful. Microsoft WordPad , launched in 1995 as a word processor for basic file editing and formatting, is finally being removed from all editions of Windows, starting with Windows 11, version 24H2, and Windows Server 2025. Microsoft WordPad The exact reason behind this removal is unclear, but Microsoft stated that most of its features, including new ones, have been added to  Notepad, which is more feature-rich than WordPad and allows users to transition seamlessly. However, many users didn’t agree, given the fact that WordPad offers more features than any plain text editor, including support for ODF and RTF file formats without requiring additional installation. Look, there could be many more reasons why users might need the WordPad back, but if the built-in support for ODF and RTF file formats is one reason, then note that you can open and edit these files using Microsoft Word , LibreOffice , or OnlyOffice . Microsoft Word LibreOffice OnlyOffice Moreover, if there is any other reason you want the original WordPad  back on your Windows 11 and 10 system, then read the entire article to  learn how to install WordPad on Windows 11 and 10 in the right way. How to Install WordPad on Windows 11, 10 Winaero is a popular website that focuses on providing high-quality free apps,  themes, and tutorials for Windows. It’s a trusted site that has been serving millions of users since 2011. Winaero It offers the original WordPad package without any tampering and  supports both 32-bit and 64-bit systems. If you dislike the app after  installation, you can quickly remove it using the uninstaller. I’ve tried and tested it on my Windows 11 system, and to be frank, it  ran just like any other Windows built-in app; to be honest, I kind of  liked it—it gives you a nostalgic, childlike feeling. To quickly install WordPad on Windows 11 and 10, follow these instructions. First, download the WordPad installer for Windows 11 and 10. Once the download is complete, go to the download folder, extract the compressed file, and double-click the extracted file to open the setup wizard (approve the UAC prompt). When the setup wizard opens, continue by clicking “Next.“ First, download the WordPad installer for Windows 11 and 10. First, download the WordPad installer for Windows 11 and 10. download the WordPad installer Once the download is complete, go to the download folder, extract the compressed file, and double-click the extracted file to open the setup wizard (approve the UAC prompt). Once the download is complete, go to the download folder, extract the compressed file, and double-click the extracted file to open the setup wizard (approve the UAC prompt). When the setup wizard opens, continue by clicking “Next.“ When the setup wizard opens, continue by clicking “ Next. “ Next. Next, it displays the default installation location; I recommend not changing it and continuing by clicking “Next.“ Next, it displays the default installation location; I recommend not changing it and continuing by clicking “ Next. “ Next. Here, it will ask whether to install WordPad for the current user or for all users. If you want to install it only for yourself, select the “For the current user only” option. Otherwise, leave the options unchanged, and continue by clicking “Next.“ Here, it will ask whether to install WordPad for the current user or for all users. If you want to install it only for yourself, select the “ For the current user only ” option. Otherwise, leave the options unchanged, and continue by clicking “ Next. “ For the current user only Next. Finally, click “Install” to start the WordPad installation. Finally, click “ Install ” to start the WordPad installation. Install The installation will be completed within 3 to 4 seconds. Once the installation is complete, the final finish window will appear, where you can select the “Run WordPad” option to open WordPad immediately after clicking “Finish.“ Once the installation is complete, the final finish window will appear, where you can select the “ Run WordPad ” option to open WordPad immediately after clicking “ Finish. “ Run WordPad Finish. You can now enjoy WordPad on your Windows 11 and 10 systems. You can now enjoy WordPad on your Windows 11 and 10 systems. How to Uninstall WordPad on Windows 11, 10 To uninstall WordPad, from Windows 11 and 10, open “ Settings “, go to “ Apps “, then “ Installed apps “, find “ WordPad ” in the list, click the three dots next to it, and choose “ Uninstall ” from the menu. Settings Apps Installed apps WordPad Uninstall Wrap Up WordPad has been closest to the hearts of most of the Windows users, including myself. It was one of the first or second Windows apps  introduced to me during my childhood. Hearing about its removal left me unaffected, as I have since transitioned to many more advanced editors  over the years. However, while writing this article, I installed and used WordPad for a while, which sparked nostalgic memories from my childhood and created a heartwarming feeling. If you’re a WordPad enthusiast, I hope you found this article useful.

How to Install WordPad on Windows 11, 10 (in the Right Way)

Stories, News & Mentions about WINDOW

Window’s Stories on HackerNoon