numpy.char.capitalize(a)

Original Documentation

Return a copy of a with only the first character of each element capitalized.

Calls str.capitalize element-wise.

For 8-bit strings, this method is locale-dependent.

Parameters:

• a: array_like of str or unicode: Input array of strings to capitalize.

Returns:

• out ndarray: Output array of str or unicode, depending on input types

See also

str.capitalize

Examples

Epic Games have just released a new set of tools aimed at making the lives of Blender users easier when working with Unreal Engine.  The tools consist of two projects, Send to Unreal and UE to Rigify.  Both are available on the Epic Games Github page, although you need to link your GitHub to your Epic account before it will work, instructions are available here.

Send to Unreal is a set of tools enabling you to easy export from Blender completely rigged, textured and animated meshes with a single menu selection.  Send To Unreal documentation is available here.

UE to Rigify goes in the other direction and enables you to import Unreal Engine rigs into Blender and make them compatible with Rigify (which needs to be enabled separately).  UE to Rigidy documentation is available here.

You can see the new Blender Tools in action, including a step by step tutorial on using Send To Unreal, in the video below.  It should be noted that you need to configure Blender to use Unreal Engine 0.01 scale, which I personally found extremely buggy in the current release.  Details on scene scale are available here, however at time of writing following these instructions caused Blender to crash every time I copied an armature into the Rig folder.  There is a good chance I did this part incorrectly in the tutorial, but it’s the only way I found to successfully export while not crashing Blender!

[embedded content]

Art GameDev News Blender Unreal

<!–

–>

Daniel

With the release of Visual Studio 2019 16.7 Preview 4, you can now try out our new experimental Razor editor for local development with MVC, Razor Pages, and Blazor. We’re excited for you to give it a try!

Enabling the new Razor editor

To enable the new experimental Razor editor in Visual Studio 2019 16.7 Preview 4 or later:

1. Install the latest Visual Studio preview

2. Go to Tools > Options > Environment > Preview Features and select the Enable experimental Razor editor option:

   

3. Select OK and restart Visual Studio

That’s it! You’re now setup to use the new Razor editor when working with Razor files locally (.cshtml and .razor).

What is Razor?

Razor is a templating language based on HTML and C# used to define dynamic rendering logic for .NET web apps based on MVC, Razor Pages, and Blazor. In MVC and Razor Pages apps you use Razor to define the rendering logic for your views and pages using .cshtml files. In Blazor, you use Razor to author reusable UI components in .razor files. Razor is a critical part of the experience for building web apps with .NET.

You can give Razor a try today by building your first web app with ASP.NET Core or Blazor.

Why a new Razor editor?

Part of the value of Razor is the rich tooling experience Visual Studio provides for editing Razor files. Visual Studio today provides IntelliSense, completions, and diagnostics for HTML, CSS, JavaScript, C#, and Razor specific syntax all within the same Razor file.

Visual Studio does some tricky gymnastics to enable editor support for all of these languages at the same time in Razor files. The Razor document is parsed to determine its constituent parts, and then each part is projected into a language specific buffer called a projection buffer. What you see in Visual Studio when editing a Razor document are a collection of little windows into each of these projection buffers to make up one whole document. Each language service then independently handles the editing experiences for each of these separate projection buffers.

For example, consider the following Razor code:

@{ ViewData["Title"] = "About";

}

<script type="text/javascript"> alert("Hello, World!");

</script>

The way Visual Studio handles this Razor code looks something like this:

This project buffer setup works well for Visual Studio and Visual Studio for Mac, but it’s problematic for remote editing scenarios, like Visual Studio LiveShare or Visual Studio Codespaces. It also can’t be used for editors that don’t have projection buffer support, like Visual Studio Code. The lack of a central orchestrator for the Razor editor also makes it difficult to enable new features without careful coordination between the various language service implementations (since they each control their own experience in projected scenarios).

A Razor Language Server

To enable broader support for Razor editing, we have been working for some time on a new Razor editor for ASP.NET Core projects based on a Razor Language Server. This new Razor Language Server implements editor features like auto completion, go to definition, etc. through the Language Server Protocol (LSP), which defines a standard way for an editor or IDE to enable these features. An IDE specific Razor extension then handles coordinating with the Razor Language Server and the other language servers for HTML & C#.

This new Razor Language Server is already being used to enable Razor support in Visual Studio Code as part of the C# extension. It will be the basis for the Razor editing support in Visual Studio Codespaces and Visual Studio LiveShare. And now it is available for local development in Visual Studio as a preview feature.

Currently our focus has been on making the new LSP based Razor editor have functional parity with the existing Visual Studio Razor editing experience (as noted below, there are still a few functional gaps to address). In future releases we expect to fill these functional gaps add significant new functionality, like bringing many more of the C# editing features to Razor, and enabling other new Razor specific productivity improvements.

Known issues

The new Razor editor is currently experimental and has some known limitations. The following Razor editor features have not yet been fully implemented and will be added in a future release:

• JavaScript and CSS IntelliSense support
• Colorization for C#, JavaScript, CSS, Blazor components, Tag Helpers, and tooltips
• Formatting is limited to only C# code in @code and @functions blocks with no embedded HTML markup or Razor syntax
• URL picker support in HTML
• C# snippets (‘prop’, ‘ctor’, etc.)
• Complex C# completions (for example, generating overrides)
• Go-to-definition/implementation from C# to Razor
• Renames in C# files do not propagate to Razor files
• Matching identifier highlight support for HTML and curly braces

There are also some functional issues with the new Razor editor in 16.7 Preview 4 that will be addressed in a future release:

• C# error squiggles may be misaligned
• Unnecessary informational errors reported for unnecessary using directives in Razor files
• Blazor components & Tag Helpers are currently colored like C# classes and don’t respect the Tag Helper colorization option

Give feedback

These are still the early days for the new LSP-based Razor editing experience in Visual Studio. We know that there’s still a lot of work to do before it can replace the existing Razor editing experience in Visual Studio. The new Razor tooling will remain optional and experimental in 16.7 and we don’t expect to make it the default Razor editor until it surpasses the functionality of the existing editor. But, we wanted to share our progress as early as possible to start getting your feedback on how well the new Razor editor works for you. To ensure we ship the best Razor editing experience possible, please give the new Razor tooling a try and let us know what you think. You can share your feedback with us by creating Razor Tooling issues on Github in the ASP.NET Core repo. We appreciate your feedback!

Apple on Thursday offered an inside look at Apple Sanlitun, the company’s latest retail location in China.

Today, Microsoft released the preview of Azure IoT Connector for FHIR—a fully managed feature of the Azure API for FHIR. The connector empowers health teams with the technology for a scalable end-to-end pipeline to ingest, transform, and manage Protected Health Information (PHI) data from devices using the security of FHIR® APIs.

Telehealth and remote monitoring. It’s long been talked about in the delivery of healthcare, and while some areas of health have created targeted use cases in the last few years, the availability of scalable telehealth platforms that can span multiple devices and schemas has been a barrier. Yet in a matter of months, COVID-19 has accelerated the discussion. We have an urgent need for care teams to find secure and scalable ways to deliver remote monitoring platforms and to extend their services to patients in the home environment.

Unlike other services that can use generic video services and data transfer in virtual settings, telehealth visits and remote monitoring in healthcare require data pipelines that can securely manage Protected Health Information (PHI). To be truly effective, they must also be designed for interoperability with existing health software like electronic medical record platforms. When it comes to remote monitoring scenarios, privacy, security, and trusted data exchanges are must-haves. Microsoft is actively investing in FHIR-based health technology like the Azure IoT Connector for FHIR to ensure health customers have an ecosystem they trust.

FHIR to fuel the Internet of Medical Things

FHIR (Fast Healthcare Interoperability Resources) is now the interoperability standard for secure and private exchange of health data. FHIR began as an open source framework for clinical data, but it’s growing adoption makes it an ideal technology to bring together data from the growing “Internet of Medical Things” (IoMT) and expand healthcare in remote monitoring scenarios.

Today remote data capture often requires device-specific platforms, making it difficult to scale when new processes are added or if patients use multiple devices. Developers have to build their own secure pipelines from scratch. With the Azure IoT Connector for FHIR available as a feature on Microsoft’s cloud-based FHIR service, it’s now quick and easy for health developers to set up an ingestion pipeline, designed for security to manage PHI from IoT devices. The Azure IoT Connector for FHIR focuses on biometric data at the ingestion layer, which means it can connect at the device-to-cloud or cloud-to-cloud workstreams. Health data can be sent to Event Hub, Azure IoT Hub, or Azure IoT Central, and is converted to FHIR resources, which enables care teams to view patient data captured from IoT devices in context with clinical records in FHIR.

The key features of the Azure IoT Connector for FHIR include:

• Conversion of biometric data (such as blood glucose, heart rate, or pulse ox) from connected devices into FHIR resources.
• Scalability and real-time data processing.
• Seamless integration with Azure IoT solutions and Azure Stream Analytics.
• Role-based Access Control (RBAC) allows for managing access to device data at scale in Azure API for FHIR.
• Audit log tracking for data flow.
• Helps with compliance in the cloud: ISO 27001:2013 certified, supports HIPAA and GDPR, and built on the HITRUST certified Azure platform.

Microsoft customers are already ushering in the next generation of healthcare

As the delivery of healthcare shifts outside the exam room, new FHIR-enabled technology is fueling IoT scenarios across the ecosystem of Microsoft’s customers.
Here are few of the great solutions already underway:

Humana’s Conviva Care Centers transform care for chronic conditions with IoT and FHIR

Conviva Care Centers, Humana’s senior-focused primary care subsidiary, will be using the Azure IoT Connector for FHIR this fall as Humana accelerates remote monitoring programs for patients living with chronic conditions. Congestive heart failure patients who monitor their weight and blood pressure at home will be able to use a new platform that enables easy sharing of data with their care team. Data from in-home devices, like scales and blood pressure cuffs, can be transferred via Azure IoT Connector for FHIR, providing doctors and nurses real-time data managed in a highly secure and private pipeline and allowing for proactive virtual touchpoints. Humana’s flexible remote monitoring platform will not only ensure patients have the support they need between clinic visits, but will also accelerate the future of user-centric care.

“Using the Azure IoT Connector for FHIR will open up new remote care paths for patients living with chronic conditions. Being able to make decisions with data coming in real time from home devices will be the game changer for improving the quality and timeliness of patient care.” —Marc Willard, Senior Vice President of Digital Health and Analytics at Humana

Sensoria Health’s Motus Smart—powered by Sensoria—is the new gold standard for enabling diabetes rehabilitation with remote monitoring

Motus Smart, powered by Sensoria, is a cutting-edge device used to provide remote patient monitoring quantified patient adherence and activity data to manage patients with diabetic foot ulcers and reduce amputation risk. Sensoria was able to deploy the Azure IoT Connector for FHIR to enable highly secure data exchange from the Motus device to patients, their doctors, and others within their circle of care. Clinicians at the Rancho Los Amigos National Rehabilitation Center are using enterprise-class applications to see real-time data, proactively reach out to patients, and address any issues that might be impeding proper treatment.

Centene connected health data platform helps manage chronic diseases

Centene is using Azure IoT Connector for FHIR in an effort to better manage the ever-expanding personal bio-metric data resulting from the proliferation of wearables and other medical devices. The company is leveraging the connector to explore the use of near-real-time monitoring and alerting as part of its overall priority on improving the health of its members, enabling them to take better care of themselves, and supporting its care management staff with actionable insights to improve the health of the communities Centene serves. In the future, Centene intends to use the connector to monitor and manage chronic conditions such as congestive heart failure, diabetes, and high-blood pressure. By leveraging Microsoft’s scalable, open platforms, Centene can make further progress toward improving outcomes for Centene Health Plan members.

Learn more and get started

We’re excited about the way our customers are embracing and delivering transformative care with FHIR technology. As we bring down the barriers of interoperability with new FHIR-based tools, the future vision of how we can evolve healthcare starts to unfold and it’s inspiring.

Microsoft has expanded the tools in our FHIR ecosystem to include IoT pipelines, so our customers have easy to use, interconnected tools for responsibly managing patient health data. Whether you’re building clinical applications, analytics engines, or developing artificial intelligence (AI) with telehealth and remote monitoring, we want to make sure you have pipelines for PHI data with security in mind. Check out the Azure IoT Connector for FHIR and the Azure API for FHIR to get started today!

Read more about the Microsoft Cloud for Healthcare, which brings together our integrated capabilities, like our FHIR tools, with robust cloud capabilities specific to customers and partners in the healthcare industry. The Microsoft Cloud for Healthcare enriches patient engagement and connects health teams to help improve collaboration, decision-making, and operational efficiencies.

FHIR® is the registered trademark of HL7 and is used with the permission of HL7.

Famitsu’s Japanese chart figures are now in for 6th – 12th July, revealing that Animal Crossing: New Horizons has been knocked off top spot.

The game has been dominating the chart for the majority of its time on sale, but this week’s new entry eBaseball Powerful Pro Baseball 2020 managed to debut in number one and two on Switch and PS4 respectively. If you’re unaware, the game is a popular, cutesy take on the sport released by Konami.

Sword Art Online: Alicization Lycoris was the only other newcomer in the top ten this week, with the rest being made up of Nintendo’s usual heavy-hitters.

Here are the top 10 (first numbers are this week’s estimated sales, followed by total sales):

1) [NSW] eBaseball Powerful Pro Baseball 2020 (Konami) {2020.07.09} – 94.876 / NEW
2) [PS4] eBaseball Powerful Pro Baseball 2020 (Konami) {2020.07.09} – 91.547 / NEW
3) [PS4] Sword Art Online: Alicization Lycoris (Bandai Namco Games) {2020.07.09} – 73.331 / NEW
4) [NSW] Animal Crossing: New Horizons (Nintendo) {2020.03.20} – 56.160 / 5.114.386
5) [NSW] Ring Fit Adventure (Nintendo) {2019.10.18} – 44.261 / 1.137.060
6) [NSW] Clubhouse Games: 51 Worldwide Classics (Nintendo) {2020.06.05} – 20.094 / 215.305
7) [NSW] Mario Kart 8 Deluxe (Nintendo) {2017.04.28} – 10.878 / 3.025.958
8) [NSW] Pokémon Sword and Shield (Pokémon Co.) {2019.11.15} – 7.857 / 3.654.961
9) [NSW] Splatoon 2 (Nintendo) {2017.07.21} – 7.450 / 3.486.199
10) [NSW] Super Smash Bros. Ultimate (Nintendo) {2018.12.07} – 6.900 / 3.751.780

Switch hardware sales saw a bit of a boost this week. Here are this week’s figures, followed by lifetime sales in brackets:

Nintendo Switch: 72,283 (11,808,351)
PlayStation 4: 1,704 (7,625,750)
PlayStation 4 Pro: 1,721 (1,566,288)
Xbox One S: 22 (21,399)
Xbox One X: 13 (20,609)

Nintendo Switch Lite: 24,596 (2,391,091)
New Nintendo 2DS LL: 732 (1,137,168)
New Nintendo 3DS: 69 (5,888,067)

< Last week’s charts

Any surprises this week? Let us know in the comments.

Update (Wed 15th Jul, 2020 16:30 BST): Route 59 Games has provided an update on the Switch edition of Necrobarista, confirming that it’s now scheduled to launch for the system in 2021.

A new trailer has been released today to celebrate the game’s launch on Steam next week. You can check that out above.

Discover a tale of mystery, magic, and, depending on who asks, the best/worst coffee around. Hidden in an unassuming alleyway lies The Terminal, a café that serves as a waypoint between the lands of the living and the dead, where any one of the patrons could be a spirit from beyond. With strict rules defining how long ghosts can spend in the corporeal realm before being forced to pass on, running this café is more complicated than your typical Melbourne coffeehouse.

Apprentice necromancer Maddy has just taken ownership of The Terminal and all its magical responsibilities. Follow her story and those of mechanics-obsessed teen Ashley, infamous Australian outlaw Ned Kelly, exasperated necromancer Chay, and a cast of other colorful characters through their dark pasts and the secrets behind the place linking them all together.

Original Article (Mon 13th Aug, 2018 17:15 BST): Route 59 Games has revealed a brand new trailer for its upcoming visual novel Necrobarista, a game headed to switch in “early 2019”.

In a magical Melbourne cafe, the dead have returned for one last night and one last cup of coffee. In this cel-shaded visual novel and adventure game hybrid, players are asked to take a break and enjoy a hot drink with a host of colourful characters – both living and dead. Dynamically-shot story vignettes set the scene, before allowing you to explore a supernatural setting in greater detail with 3D point-and-click adventure sessions.

The trailer certainly sets up what could be an interesting adventure to explore, but gameplay details are still rather few and far between this far away from the game’s launch. If the anime-inspired visuals have you intrigued, however, you might want to check out this feature list below.

Features:
– Stylised cinematic presentation inspired by anime aesthetics.
– Discover the world of fantasy Melbourne through dozens of intersecting stories.
– Explore the Terminal through free-roaming first-person scenes.
– Featuring Goon-sack robots, Alchemical coffee, and Ned Kelly.
– Soundtrack by Kevin Penkin, composer for Under the Dog, Norn9, and Made in Abyss.
– Multi-lingual support: English, Chinese, and Japanese.

Do you have any early impressions on this one that you’d like to share? Let us know your thoughts below.