propagator | Centralized schema & data deployment | Continuous Deployment library

Short version

As suggested in comments, I am leaving a summarized, short version of the problem I found here. The original complete explanation can be found below.

In summary, I am currently using the deSolve package and am interested in implementing events in response to root functions. I understand that I can use such events to introduce sudden changes in the state variables of the model, but I would like to also modify parameter values of the model in response to such root functions.

Is this possible?

Long version

I have implemented an orbital numerical propagator (a function to calculate the position of a space satellite given an initial position and velocity state) in R. The problem is formulated as a set of 6 ODEs (X, Y and Z components for position and velocity). My implemented models calculate the acceleration at any given time, and then I use the deSolve package to perform integration and calculate the trajectory.

A key parameter that must be decided when performing such calculation is the center of the frame of reference, which is usually placed at the center of mass of the celestial object that exerts the most significant gravitational influence on the satellite. This is because, even though in principle it is possible to perform integration and calculate the trajectory using any arbitrary frame of reference, in practice we only obtain reasonable results when the center of coordinates is placed on the celestial object that exerts the main gravitational influence (i.e., Earth for Earth-orbiting satellites, Moon for Moon-orbiting satellites, and so on), as discussed in this SE question.

Initially, my implementation used a constant center of coordinates, either provided by the user or automatically determined from the sphere of influence of the different main celestial objects.

However, this is not appropriate for modeling interplanetary space missions, since the celestial object that exerts the main gravitational influence changes during the trajectory. A good example is the Apollo missions, where satellites started in an Earth orbit, and then moved to a Moon orbit.

I have managed to detect when such changes of the central celestial object happen, and return it as part of the results of the integrator. However, in order to actually perform the correct modeling, the central body being used during integration needs to be changed when these changes are detected. This process of "changing the central body" involves two tasks (note that it is just a shift of the center of coordinates, with no rotations involved):

1. Subtracting the coordinates of the celestial body to be used as the new center of coordinates from the coordinates of the satellite (by doing so, the coordinates of the satellite are now referred to the new celestial body).
2. Modifying the value of the argument specifying the central celestial body that is passed to the function calculating acceleration, which is one of the elements of the list of parameters provided to the function defining the ODE model.

I believe Task 1 can be easily solved by using a root-activated event. In order to do so, I define a variable in an environment specifically created for this purpose that stores the value of the automatically calculated celestial body that exerts the main gravitational influence in each iteration of the integrator. At a new iteration, a new value is calculated, and is compared with the previous value. If it is the same, nothing happens. But if it is different, a root function would return 0, triggering an event function. The event function would then return the position minus the coordinates of the new central celestial body.

However, I am unsure about how to perform Task 2, since this would involve changing one of the initial parameters provided to the ODE model. Any ideas on this would be greatly appreciated! (either a continuation of my approach, or a completely different one).

I am leaving a simplified version of the involved code.

My main function is called hpop, and is the user-level function to which the initial state vector and other parameters are passed. It looks like this:

I'm trying to test some opentelemetry spans are correctly build and linked in parent child relations.

I've got an WPF application I'm writing, however whilst testing the insert of a record I'm getting the below exception.

The Application is using .NET 4.8, I'm using Entity Framework 5.

The exception I'm getting is:

How do I get route propagation working in a Nextjs Shopify app?

I'm building a Shopify App scaffolded with the CLI and have issues with routing using the Nextjs router. The standard embedded app implementation does not update the URL so a RoutePropagator component is needed.

I implemented Shopify's RoutePropagator but got the error TypeError: Cannot read properties of undefined (reading 'pathname')

Then I found this implementation which works for updating the URL, but runs into a really strange issue for Dynamic Urls.

Whenever a user navigated to a dynamic url, the url would update with [id] in the url. Gif example:

Narrowing it down, the below snipped causes the above dynamic url issue:

I'm trying to get OpenTelemetry tracing working with FastAPI and Requests. Currently, my setup looks like this:

I am trying to integrate Opentelemetry (Otl) in my Angular application to trace the frontend calls. Everything works fine and I am able to see the calls in the Zipkin.

But the only problem is that it is showing it as "unknown_service" in the Zipkin interface.

Below is my entire Angular code and Zipkin screenshot as well. This is just a sample application. But my requirement is that I am going to integrate the Opentelemetry code in the http interceptor so that it will be easy to maintain at one place instead of every service call. Also service.name should be passed dynamically so that it will be traced in Zipkin.

How can I add a service name before it gets called?

I am trying to export metrics and traces from my Akka app written in Scala using OpenTelemetry agent with the purpose of consuming the data in OpenSearch.

Technology stack for my application:

• Akka - 2.6.*
• RabbitMQ (amqp client 5.12.*)
• PostgreSQL (jdbc 42.2.*)

I've added OpenTelemetry instrumentation runtime dependency to build.sbt:

I'm running a Python gRPC server on Cloud Run and attempting to add instrumentation to capture trace information. I have a basic setup currently, however I'm having trouble making use of propagation as shown in the OpenTelemetry docs.

Inbound requests have the x-cloud-trace-context header, and I can log the header value in the gRPC method I've been working with, however the traces created by the OpenTelemetry library always have a different ID than the trace ID from the request header.

This is the simple tracing.py module I've created to provide configuration and access to the current Tracer instance: