Model: Collab-uniba/fprime-binary-setfit
Author: Collab-uniba
Pipeline: text-classification
Library: setfit
Tags: setfit, safetensors, mpnet, sentence-transformers, text-classification, generated_from_setfit_trainer, arxiv:2209.11055, region:us
Card metadata: library_name: setfit
metrics: accuracy
pipeline_tag: text-classification
tags: setfit, sentence-transformers, text-classification, generated_from_setfit_trainer
widget: Throttle send frame EVR
| | |
|:---|:---|
|**_F´ Version_**|commit d3fa31c |
|**_Affected Component_**| ?  |
---
## Problem Description

A description of the problem with sufficient detail to understand the issue.

If there is no ground system, the interface continuously sends this pair of EVRs:

```
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x201db690 (TV_TLM): [ERROR] Failed to send framed data: 0
0x202236f0 (TV_ReceiveTask): [WARNING] Failed to open port with status 61 and errno 0
```

## How to Reproduce

1. Run Ref without the ground system
2.
3.

## Expected Behavior

IMHO the EVR should throttle, and perhaps the throttle is reset when the connection is make.
, Color-coding interlaced Events in the API Log
| | |
|:---|:---|
|**_F´ Version_**| |
|**_Affected Component_**|  |
---
One feature that wasn't completed this summer was to color-code interlaced event logs based on severity. Presently, interlacing events are implemented by making the API a consumer of the event decoder in the GDS and then filtering events. Modifying the color of these log messages can be done [here](https://github.com/nasa/fprime/blob/717bc6fab85c53680108fc961cad6338e779816f/Gds/src/fprime_gds/common/testing_fw/api.py#L1258).
, Switch Framer and Deframer to use Mallocator Pattern
| | |
|:---|:---|
|**_F´ Version_**| |
|**_Affected Component_**|   |
---
## Problem Description

Mallocator pattern is preferred over member-allocated buffers., Ninja support for fprime-tools
| | |
|:---|:---|
|**_F´ Version_**| |
|**_Affected Component_**|   |
---
## Problem Description

There are a couple places in fprime-tools where things would break if Ninja was used instead of Make. We need to fix that, as Ninja is usually much faster.
e.g. [this](https://github.com/fprime-community/fprime-tools/blob/0a9fdf58ce4b428d407ab264f7266041808237c8/src/fprime/fbuild/cmake.py#L133) is Make-specific output, Ninja formats it differently

## Expected Behavior

Support Ninja with fprime-tools. Add a convenient option to chose which one to use.
, Build A Frame Reassembler
| | |
|:---|:---|
|**_F´ Version_**| |
|**_Affected Component_**|  |
---
## Feature Description

Build a component that can be used to reassemble communication frames given protocol information. This will break-off this functionality from the Deframer.

Basic requirements:
1. Accept incoming Fw::Buffers of any size
2. Accumulate buffers in-order
3. Call frame detector helper class
4. On "NO_FRAME" discard first byte and try again
5. On "NEED DATA" continue to accumulate data
6. On "FRAME" allocate buffer, copy-out frame

Helper class requirements:
1. Must implement `Enum detect_frame(const CircularBuffer& buffer, FwSizeType& size_output)` method
2. Cannot alter circular buffer (uses peeks)
3. Must set `size_output` when data is needed and when frame detected
 
inference: yes
Likes: 0 | All-time downloads: 83
Created: 2024-10-22 15:12:08