Another atmosphere preview zip

Consider the ReSwitched discord's hack-n-all channel for your educational purposes. We are at least for now using catch2 for unit tests. Almost all virtual calls in the kernel are now resolved statically. This eliminates substantial virtual call overhead, and should lead to improved kernel microperformance in pretty much every function. The remaining red black tree find operations which weren't using the optimized "find key" variant are now using the optimized version.

Custom assembly was written to improve tick-to-timespan conversion. This works around gcc emitting suboptimal assembly at -Os it emits good assembly at -O3, clang is fine at both -O3 and -Os. Rather than unnecessarily zero-ing all data in kernel objects only to overwrite members later, we now only initialize the members we need to in kernel object constructors. This is what Nintendo was doing already.

This should strictly improve microperformance of many system calls. An compile-time toggleable extension was added to support bit physical addresses in MapRange capabilities using currently reserved bits. A number of minor bugs were fixed, including: Initial cache management now better reflects official behavior. This fixes an issue that caused certain hardware with cache sensitivity to produce cryptic kernel panics during boot.

Incorrect logic when checking thread priority capabilities was fixed to reflect official behavior. Accesses to the processes local region were fixed to properly use kernel linear region, not userland pointers. The cache SVCs exposed for bit processes now better reflect official core mask request semantics.

A bug was fixed that could cause a kernel panic if SvcArbitrateLock was called on a thread with exactly one reference in the middle of handling a user-mode exception. The following was changed since the last release: Support was implemented for This facilitates writing unit tests for the kernel and other atmosphere components and running them under PC.

This should hopefully allow us to have greater confidence that all of atmosphere's components work the way they're theoretically supposed to in the future.

This should fix any issues that might result from running older releases on the OLED model, if you're somehow in a position to do so. The "target firmware" system was changed to allow the bootloader to specify an approximation, rather than the true target firmware. This greatly simplifies bootloader requirements, and correspondingly all code for accessing SYSTEM has been removed from fusee.

This should result in a substantial speedup when booting emummc with fusee, as SYSTEM accesses were the most expensive thing done previously.

This should resolve any inconsistency in firmware detection when booting via fusee vs hekate. This should also improve our compatibility with micro firmware releases, making it more likely that atmosphere "just works" if nothing important has changed. Dynamic resource limit determination logic was implemented in pm to match latest official behavior.

An enormous amount of refactoring was performed under the hood, including: Please Note : If you are a developer who uses Atmosphere-libs, a number of changes here are breaking. Feel free to contact SciresM for help updating your program.

Since mesosphere is now always-on, os::LightEvent which required newer SVCs is now globally usable and used by stratosphere where relevant. Assertions are now true no-ops when building for release. Most "common" logic in system module main. Please Note : main. A number of longstanding code style issues were corrected. Mesosphere now puts its relocation table inside. The spl and loader system module was refactored to better reflect official logic. Many, many other minor changes, please talk to SciresM or read the relevant commits if you want to know more.

The following was changed since the last release: A bug was fixed which caused some memory to leak when launching a game with mods enabled, eventually causing a crash after enough game launches without rebooting. Two new services "sprofile" were added to erpt , and have been fully reimplemented. Please Note : These services provide a way for settings to be pushed to consoles over the internet without system update.

Because there appear to be no settings pushed out yet, this implementation fundamentally cannot be fully tested right now, but hopefully there are no issues once settings begin being distributed. The LogManager system module was reimplemented. This system module provides services that some games use for logging. Atmosphere's reimplementation supports logging to the SD card if lm!

To control the directory where logs are saved, modify the lm! Atmosphere's reimplementation is disabled by default in order to save memory , but can be enabled by setting lm! This will allow reading over logs from games which use the services or potentially logging from homebrew in the future , which can be useful to developers.

The rewrite was performed with a big emphasis on ensuring a good boot speed, and generally boot should be much faster than it was previously. The obvious low-hanging fruit for performance improvements has been picked, so hopefully the improved performance is to everybody's liking. SD card compatibility was improved: fusee should now have SD card compatibility identical to the official OS driver. Please Note : various components were renamed fusee-primary.

If you use another bootloader like hekate , you may need to update your configuration to use the new layout. Please Note : BCT. If you rely on custom nogc configuration, please be sure to update accordingly.

To compensate for this, a script to insert a custom splash screen into a package3 binary has been added to the utilities folder of the atmosphere repository. NCM is no longer opt-out. The following was changed since the last release: An issue was fixed that caused severely degraded performance after wake-from-sleep on Mariko hardware. This was due to Mariko MTC resulting in a frequency of Assets 5 atmosphere A Macroclass is a group of ROIs having different Class ID, which is useful when one needs to classify materials that have different spectral signatures in the same land cover class.

For instance we could classify grass e. Macroclass example. Vegetation: trees. Vegetation: grass. After the collection of several ROIs, it is useful to display the spectral signatures thereof, in order to assess the spectral similarity:. You can download the final training shapefile and spectral signature list , where 11 spectral signatures were collected.

SCP allows for classification previews , in order to assess very rapidly the classification results. Classifications previews are useful during the collection of ROIs, and for the selection of the more accurate spectral signatures. If the preview results are considered good i.

Otherwise, it is possible to remove one or more spectral signatures, or add new spectral signatures creating other ROIs as described in Collection of ROIs and Spectral Signatures. The final land cover classification can be downloaded from here.

The accuracy assessment of land cover classification is useful for identifying map errors. SCP allows for the calculation of accuracy comparing the classification raster to a reference shapefile.

Usually, accuracy assessment requires ancillary data and field survey. In this tutorial we are are going to compare the land cover classification to the training ROIs. The following error matrix represents the number of pixels classified correctly in the major diagonal. As you can see, most of the errors are between class 3 built-up and 4 bare soil.

From the error matrix file, we have also calculated the accuracy of user and producer; the results show that class 4 bare soil has high commission error - user accuracy and low omission error - producer accuracy. In order to improve the results, we should collect more ROIs and spectral signatures for the bare soil class, paying attention to the spectral similarity with the built-up class.

SCP allows for the calculation of a classification report with the percentage and the area of land cover classes. Of course, these figures are the result of a tutorial for demonstrating the main features of the SCP for the land cover classification of a Landsat image; several ROIs for each class are required for a good classification only 11 ROIs were collected in this tutorial , considering their spectral variability; also, field data is useful for improving the collection of ROIs and spectral signatures.