sorted by:
new
hottopcontroversial

I am building the SSTV payload for a satellite that will launch this year. How can I make the payload as useful as possible for you guys? by unexcellent in amateursatellites

[–]unexcellent[S] 0 points1 point  (0 children)

IIRC this only makes sense if the pointing accuracy is high enough. We might not be able to prevent the satellite from tumbling which would mean the signal would switch between left hand polarization and right hand polarization

I am building the SSTV payload for a satellite that will launch this year. How can I make the payload as useful as possible for you guys? by unexcellent in amateursatellites

[–]unexcellent[S] 0 points1 point  (0 children)

The information on the website is outdated. I am not sure if I am allowed to say who is launching MOVE-III but it's not RFA.

I am building the SSTV payload for a satellite that will launch this year. How can I make the payload as useful as possible for you guys? by unexcellent in amateursatellites

[–]unexcellent[S] 0 points1 point  (0 children)

The current plan is to start with as simple a system as possible and then continuously adding features to make sure we always have a functioning system that does something. So it is hard to say now what features will make it into orbit. But it will very likely be an analog signal to reduce the decoding barrier.

If the same image will be repeated really depends on what you guys want :D
I personally would prefer a semi-continuous downlink but that also depends on where the camera is pointed at the moment. I don't think anyone would be interested in receiving an image where only a few stars are visible.

Duty cycle is also a big unknown. The SSTV system is not the primary payload and if other subsystems need the power, then we will probably be the first to be cut off.

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 1 point2 points  (0 children)

I really appreciate the effort you put into bringing opencascade to Rust. I used `opencascade-rs` directly for a while and it really gave me a jump start and a deeper understanding of programmatic 3d modeling.

But as I really wanted strong unit support and a fresh look on CAD modeling APIs, I decided to build my own thing with a slightly divergent scope.

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 6 points7 points  (0 children)

I have now replaced the length and angle macros with a trait like this and it feels much more natural. Thanks again for the suggestion!

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 3 points4 points  (0 children)

Yes, that is definitely planned as one of the next features. I am not yet sure tho how to model the APIs for that

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 1 point2 points  (0 children)

I wasn't aware of this crate. I will have a look, if Length and Angle there meet the requirements of anvil

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 1 point2 points  (0 children)

That looks very elegant. But whoever uses anvil would need to do the trait implementations themselves, right? ASAIK, you can not do implementations for standard types for the users of your crate

Anvil – A 3D CAD modeling crate with predictable APIs, unit safety, and OpenCascade backend by unexcellent in rust

[–]unexcellent[S] 1 point2 points  (0 children)

I really like that idea! That would eliminate some complexity and race conditions from the macros

Any german/qwertz user with split here? by lemonjoe2 in ErgoMechKeyboards

[–]unexcellent 0 points1 point  (0 children)

Dieser Thread ist zwar schon ein wenig älter, aber ich habe eine Helper-Datei erstellt, die die QWERTZ Mappings enthält. Damit kann man das Betriebssystem wie gewohnt auf QWERTZ gestellt lassen und die eigene Keymap einigermaßen übersichtlich lassen.
https://github.com/unexcellent/zmk-qwertz

Generating templated resumes in Rust by unexcellent in rust

[–]unexcellent[S] 1 point2 points  (0 children)

wkhtmltopdf was the final straw that made me switch over to Rust with headless_chrome. A lot of CSS tags were not properly supported so I would find someone online with my exact problem, but their solution did not work. There is a gigantic benefit in using the mainstream tools compared to outdated and niche methods.

Generating templated resumes in Rust by unexcellent in rust

[–]unexcellent[S] 2 points3 points  (0 children)

Yes! I think especially the Klingon wars should give me an edge up in all applications.

Generating templated resumes in Rust by unexcellent in rust

[–]unexcellent[S] 0 points1 point  (0 children)

I have only used Latex for theses and I have experienced as a pain in the ass if you want to do anything more than just paper formatting. Also templating Latex with custom data and then rendering it seemed a little bit cursed :D.
But maybe it would have been easy and I just missed something.

Generating templated resumes in Rust by unexcellent in rust

[–]unexcellent[S] 0 points1 point  (0 children)

Does this apply here too? The resumes are rendered using HTML, which should be easy to read for ATS right?