#FDIR
LightNews LightNews
thomasthefrench.eurosky.social
La chaîne FDIR qui fait sauter la RF. Oups !
revesdespace.eurosky.social Rêves d'espace @revesdespace.eurosky.social · 5d
pour de futures missions potentielles de désorbitation. L'anomalie est due à un défaut de son système de protection contre les pannes : ce logiciel embarqué a éteint par erreur le transpondeur.
2/3
November 5, 2026 at 10:42 AM
meowyoga.bsky.social
🤣 Actually, the end of MAGA and Trump will Make the Whole World Laugh 🌊
www.youtube.com/watch?v=fdiR...
I Started a Joke - Lyrics - Bee Gees
YouTube video by Somewheremaybe
www.youtube.com
October 21, 2026 at 10:44 PM
amias.net
It wasn't a fdir choice, the lies are still being defended by people who should be in jail for them.
October 6, 2026 at 8:05 AM
sunwardhobbies.bsky.social
Why Is My Airbrush Not Working? Video by David Peckham youtu.be/FDIR-RiympY #sunwardhobbies #freeshipping #mississauga #toronto #canada #Vigiart #vallejocolors #grexairbrush
Why Is My Airbrush Not Working?
YouTube video by Sunward Hobbies
youtu.be
September 26, 2026 at 2:46 PM
barthecloclo.bsky.social
Italie #Histoire #Archéologie découverte : les #Etrusques ♥️
www.histoire-pour-tous.fr/civilisation...
www.youtube.com/watch?v=Bnhe...
www.worldhistory.org/trans/fr/1-2...
www.youtube.com/watch?v=xOft...
www.dailymotion.com/video/x7bh92v
www.youtube.com/watch?v=fdIr...
www.youtube.com/watch?v=Oexz...
September 22, 2026 at 8:11 PM
freefloof.bsky.social
Please perform an FMEA on your FDIR and to ensure FRACAS compliance log the issues in Jira using the IRF so the IRB can assign a CAPA for V&V and QA/QC
September 18, 2026 at 12:33 PM
queenrayna1337.bsky.social
The fight scene between Bond and Patrice in Shanghai is so pretty
www.youtube.com/watch?v=fDiR...
September 14, 2026 at 2:20 AM
wago-polska.bsky.social
Chcesz dowiedzieć się co nowego w WAGO?

Zapraszamy na ENERGETAB’26
15-17 września 2026
Hala A, stoisko 33

#PV #OZE #Energia #OSD #TETRA #LTE450 #OLTC #FDIR #SmartHome #HomeAutomationb #Energy #EnergyConnections #SmartGrid
September 14, 2026 at 8:10 AM
matthewfields.bsky.social
Alaskas Native population relies heavily on SNAP WIC and FDPIR. All programs targeted by Trump. Alaskans receive 2nd highest in the nation SNAP and taxing that income while removing WIC and FDIR would be catastrophic. The bill is terrible for the US but worse for Alaska.
July 2, 2025 at 1:05 PM
suhnih.kawaii.social
youtube.com/watch?v=FdIr...
youtube.com
December 1, 2024 at 4:25 PM
pensologopenso.bsky.social
sdds FDir
November 25, 2025 at 10:08 PM
beefedai.bsky.social
FDIR Patterns for Safety-Critical Firmware

https://beefed.ai/en/fdir-patterns-embedded-firmware

#FDIR #FaultDetection #FaultIsolation #FaultRecovery #EmbeddedFirmwareDiagnostics
FDIR Patterns for Safety-Critical Firmware
beefed.ai
May 7, 2026 at 12:06 AM
educativ.bsky.social
Internship (d/f/m) in Satellite Operations and Failure Detection, Isolation and Recovery (FDIR) - Immenstaad am Bodensee Job educativ.net/jobs/job/35827...
April 17, 2025 at 3:17 PM
genejm1017.bsky.social
Issues and Key Findings & Organizational issues from the #NASA Starliner Propulsion System Investigation Report -
1. Service Module (SM) RCS Thruster Anomaly a. Five thrusters triggered fail off FDIR during ISS rendezvous resulting in a temporary loss of 6 Degrees of Freedom (6DOF) control. b. c. d. In-situ troubleshooting recovered four of five jets, enabling docking. Manual piloting did not specifically contribute to thrusters triggering their fail-off FDIR. Most probable proximate (direct) causes and contributing factors: i. Two-phase oxidizer flow (vaporization and cavitation) ii. Teflon poppet extrusion in oxidizer valves, restricting flow iii. Mechanical demand from GNC firing requests Crew Module (CM) RCS Jet Failure a. A thruster failed to fire during descent, reducing the system to zero fault tolerance. b. Leading theory: i. Corrosion from carbazic acid formed by residual propellant and CO₂ 3. Helium Manifold Leaks a. b. Seven of eight SM helium manifolds leaked during the mission. Most probable proximate (direct) cause and contributing factor: i. Material incompatibility of seals with oxidizer, leading to degradation and leaks ii. O-ring sizing and poor gland fill/squeeze tolerances 4. Deorbit Capability Fault Tolerance a. The propulsion system lacked required two-fault tolerance for deorbit burns, which was a design flaw present since early development but not identified until CFT pre-launch. • Inadequate Qualification Testing: The propulsion system lacked enveloping, mission- representative testing, and NASA accepted insufficient verification data in lieu of qualification. • Insufficient Flight Data: Low telemetry sample rates and lack of onboard data storage limited the ability to assess thruster performance and contributed to misdiagnosis of anomalies on Orbital Flight Test (OFT) 1 and OFT2. • Anomaly Resolution Discipline: Acceptance of unexplained anomalies (UAs) without root cause resolution allowed systemic issues to persist from OFT1 and OFT2 into CFT. • Oversight and Insight Limitations: NASA’s insight into subcontractor-level data was restricted, limiting its ability to independently verify system readiness. • Schedule Pressure: Persistent proximity to launch over several years created a high-stress environment, dictated a restrictive risk reduction initiative, and contributed to degraded trust with the workforce and overall fatigue. • Cultural and Contractual Misalignment: The shared accountability model was poorly understood and inconsistently applied, leading to muddling of roles, responsibilities, and risk ownership. • Hardware Longevity and Sparing Concerns: Starliner’s limited hardware spares and the impending retirement of the Atlas V launch veicle raises concerns about the program's long-term viability. Near-Real Time Cultural and Organizational Findings 1. Decision Authority • Overlapping roles between NASA’s CCP, ISSP, and Boeing led to unclear governance. 2. Erosion of Trust • Mistrust between NASA and Boeing was intensified by selective data sharing, perceived favoritism, and inconsistent transparency. • NASA teams outside CCP felt excluded from critical decisions, while CCP felt overwhelmed by external input. 3. Leadership Approach • CCP and Boeing leadership were perceived as overly risk-tolerant and dismissive of dissenting views. • A risk-acceptance posture created division and undermined confidence in the decision- making process. 4. Team Dynamics and Communication • The mission was marked by chaotic meeting schedules, unclear roles, and communication breakdowns. • Survey data shows low effectiveness ratings in team dynamics and organizational structure. 5. Cultural Divergence • NASA’s traditional culture of technical rigor clashed with the commercial model’s emphasis on provider autonomy. All of the findings explained in this report led the team to determining the following as root causes for the anomalies that occurred over the CFT: Root Causes (Organizational) While these root causes are specifically separated out to bulletize each, it is nearly impossible to consider one without the others. It is important to keep in mind, NASA created and implemented the contract structure; Boeing built the vehicle. Together the organizations agreed to fly. • NASA’s hands-off contract approach limited insight into the Starliner’s development. • Boeing’s inadequate systems engineering and reliance on subcontractors without sufficient oversight created gaps in hardware qualification. • NASA CCP’s culture prioritized provider success over technical rigor.
February 19, 2026 at 9:07 PM
ragingspirit.bsky.social
This is a very terse description of what was an absolutely terrifying experience for the people piloting the craft. Had it got any worse, chances are they would not have been able to either dock to the ISS or deorbit.
Key Technical Anomalies 1. Service Module (SM) RCS Thruster Anomaly a. Five thrusters triggered fail off FDIR during ISS rendezvous resulting in a temporary loss of 6 Degrees of Freedom (6DOF) control. b. In-situ troubleshooting recovered four of five jets, enabling docking. c. Manual piloting did not specifically contribute to thrusters triggering their fail-off FDIR. d. Most probable proximate (direct) causes and contributing factors: i. Two-phase oxidizer flow (vaporization and cavitation) ii. Teflon poppet extrusion in oxidizer valves, restricting flow iii. Mechanical demand from GNC firing requests
February 19, 2026 at 10:04 PM
grixu.dev
Looking for a Library to Search File Structures?

fdir is a lightweight Node.js library (under 2kB!) for fast, recursive file searches with custom filters. It’s part of the e8e movement, prioritizing performance and minimal dependencies: https://buff.ly/3Cbo6UE

#javascript #nodejs
GitHub - thecodrr/fdir: ⚡ The fastest directory crawler & globbing library for NodeJS. Crawls 1m files in < 1s
⚡ The fastest directory crawler & globbing library for NodeJS. Crawls 1m files in < 1s - thecodrr/fdir
buff.ly
January 27, 2025 at 6:00 AM
wolf.observer
Jesus fucking christ. Commercial spaceflight was a mistake
Key Technical Anomalies 1. Service Module (SM) RCS Thruster Anomaly a. Five thrusters triggered fail off FDIR during ISS rendezvous resulting in a temporary loss of 6 Degrees of Freedom (6DOF) control. b. In-situ troubleshooting recovered four of five jets, enabling docking. c. Manual piloting did not specifically contribute to thrusters triggering their fail-off FDIR. d. Most probable proximate (direct) causes and contributing factors: i. Two-phase oxidizer flow (vaporization and cavitation) ii. Teflon poppet extrusion in oxidizer valves, restricting flow iii. Mechanical demand from GNC firing requests 2. Crew Module (CM) RCS Jet Failure a. A thruster failed to fire during descent, reducing the system to zero fault tolerance. b. Leading theory: i. Corrosion from carbazic acid formed by residual propellant and CO₂ 3. Helium Manifold Leaks a. Seven of eight SM helium manifolds leaked during the mission. b. Most probable proximate (direct) cause and contributing factor: i. Material incompatibility of seals with oxidizer, leading to degradation and leaks ii. O-ring sizing and poor gland fill/squeeze tolerances 4. Deorbit Capability Fault Tolerance a. The propulsion system lacked required two-fault tolerance for deorbit burns, which was a design flaw present since early development but not identified until CFT pre-launch Key Findings and Observations (Truncated Summary) • Inadequate Qualification Testing: The propulsion system lacked enveloping, missionrepresentative testing, and NASA accepted insufficient verification data in lieu of qualification. • Insufficient Flight Data: Low telemetry sample rates and lack of onboard data storage limited the ability to assess thruster performance and contributed to misdiagnosis of anomalies on Orbital Flight Test (OFT) 1 and OFT2. • Anomaly Resolution Discipline: Acceptance of unexplained anomalies (UAs) without root cause resolution allowed systemic issues to persist from OFT1 and OFT2 into CFT. • Oversight and Insight Limitations: NASA’s insight into subcontractor-level data was restricted, limiting its ability to independently verify system readiness. • Schedule Pressure: Persistent proximity to launch over several years created a high-stress environment, dictated a restrictive risk reduction initiative, and contributed to degraded trust with the workforce and overall fatigue. • Cultural and Contractual Misalignment: The shared accountability model was poorly understood and inconsistently applied, leading to muddling of roles, responsibilities, and risk ownership. • Hardware Longevity and Sparing Concerns: Starliner’s limited hardware spares and the impending retirement of the Atlas V launch vehicle raise concerns about the program's long-term viability. impending retirement of t Near-Real Time Cultural and Organizational Findings 1. Decision Authority • Overlapping roles between NASA’s CCP, ISSP, and Boeing led to unclear governance. 2. Erosion of Trust • Mistrust between NASA and Boeing was intensified by selective data sharing, perceived favoritism, and inconsistent transparency. • NASA teams outside CCP felt excluded from critical decisions, while CCP felt overwhelmed by external input. 3. Leadership Approach • CCP and Boeing leadership were perceived as overly risk-tolerant and dismissive of dissenting views. • A risk-acceptance posture created division and undermined confidence in the decisionmaking process. 4. Team Dynamics and Communication • The mission was marked by chaotic meeting schedules, unclear roles, and communication breakdowns. • Survey data shows low effectiveness ratings in team dynamics and organizational structure. 5. Cultural Divergence • NASA’s traditional culture of technical rigor clashed with the commercial model’s emphasis on provider autonomy. Root Causes (Organizational) While these root causes are specifically separated out to bulletize each, it is nearly impossible to consider one without the others. It is important to keep in mind, NASA created and implemented the contract structure; Boeing built the vehicle. Together the organizations agreed to fly. • NASA’s hands-off contract approach limited insight into the Starliner’s development. • Boeing’s inadequate systems engineering and reliance on subcontractors without sufficient oversight created gaps in hardware qualification. • NASA CCP’s culture prioritized provider success over technical rigor.
February 20, 2026 at 8:36 PM
longtail-news.bsky.social
Feed: "PyPI recent updates"
Published on Friday, July 3, 2026
aether-robotics 3.11.6.4
Autonomous multi-agent robotics system with DRL-First Hybrid FDIR
pypi.org
July 3, 2026 at 9:57 PM
ai-firehose.column.social
This study presents FDIR, a two-stage architecture that harmonizes pixel fidelity, perception, and machine needs in lossy image restoration, outperforming models. FDIR bridges the gap between perception and machine learning, transforming image processing. https://arxiv.org/abs/2608.00111
FDIR: Harmonizing Fidelity and Human-Machine Preference in Lossy Compression Image Restoration
ArXiv link for FDIR: Harmonizing Fidelity and Human-Machine Preference in Lossy Compression Image Restoration
arxiv.org
August 4, 2026 at 2:10 PM
kai3690.bsky.social
## Federated Decentralized Identity Resolution for Seamless Metaverse Asset and Avatar Interoperability

**Abstract:** Current metaverse platforms suffer from fragmented identities and asset silos, hindering interoperability and user experience. This paper introduces a novel Federated Decentralized…
## Federated Decentralized Identity Resolution for Seamless Metaverse Asset and Avatar Interoperability
**Abstract:** Current metaverse platforms suffer from fragmented identities and asset silos, hindering interoperability and user experience. This paper introduces a novel Federated Decentralized Identity Resolution (FDIR) system leveraging secure multi-party computation (SMPC) and graph neural networks (GNNs) to enable seamless asset transference and avatar migration across distinct metaverse environments. By collaboratively resolving identities without centralizing user data, FDIR enhances privacy and security while unlocking unprecedented levels of metaverse interoperability.
freederia.com
December 23, 2025 at 10:04 AM
kai3690.bsky.social
## 정식 연구 자료: 자율 비행 드론의 혼합 시스템 기반 고장 진단 및 복구 전략 연구

**초록** 본 연구는 자율 비행 드론의 운용 신뢰성 향상을 목표로, 혼합 시스템 기반의 고장 진단 및 복구(FDIR: Fault Detection, Isolation, and Recovery) 전략을 제시한다. 드론의 다양한 작동 환경 및 고장 유형을 고려하여, 칼만 필터(Kalman Filter) 기반의 상태 추정, 머신 러닝(Machine Learning) 알고리즘을 활용한 고장 진단, 그리고 모델 예측 제어(Model…
## 정식 연구 자료: 자율 비행 드론의 혼합 시스템 기반 고장 진단 및 복구 전략 연구
**초록** 본 연구는 자율 비행 드론의 운용 신뢰성 향상을 목표로, 혼합 시스템 기반의 고장 진단 및 복구(FDIR: Fault Detection, Isolation, and Recovery) 전략을 제시한다. 드론의 다양한 작동 환경 및 고장 유형을 고려하여, 칼만 필터(Kalman Filter) 기반의 상태 추정, 머신 러닝(Machine Learning) 알고리즘을 활용한 고장 진단, 그리고 모델 예측 제어(Model Predictive Control, MPC) 기반의 자율 복구 알고리즘을 통합한 혼합 시스템을 설계한다. 이 시스템은 비행 중 발생하는 센서 고장, 모터 고장, 통신 오류 등 다양한 고장 상황을 신속하게 감지하고, 고장 위치를 정확하게 격리하며, 안전한 복구 경로를 계획하여 드론의 임무 수행 능력을 보존한다.
freederia.com
April 18, 2025 at 6:43 AM
pmc.bsky.social
"5+ years’ experience in mission-critical spacecraft avionics systems development (both hardware and software), including fault detection, isolation and recovery (FDIR) architecture". Sadly, I don't have that and, arguably, anyone who does wouldn't be daft enough to apply
March 27, 2025 at 7:15 PM
l422y.com
npm-check dependency reduction · Issue #131 · es-tooling/ecosystem-cleanup
repo: https://github.com/dylang/npm-check there's a few dependencies we can replace to reduce footprint: chalk (with picocolors) execa (with tinyexec) globby (with fdir or tinyglobby) is-ci (with n...
github.com
November 18, 2024 at 7:51 AM
rizzselle.bsky.social
a fdir ta emocionando muito amigas era brincadeira eu nao odeio o meu curso
October 7, 2024 at 2:24 AM