Is VSP Hangar Down?

304 views
Skip to first unread message

Olex Tkachuk

unread,
May 28, 2024, 3:17:00 AM5/28/24
to OpenVSP
Screenshot from 2024-05-28 17-13-17.png
First of all the Let's Encrypt certificate is out of date, plus 500 HTTP error form the server.

Please let me know if help is needed to fix it.

Rob McDonald

unread,
May 29, 2024, 12:31:02 AM5/29/24
to OpenVSP
Search the archives here, there are quite a few threads about it.

The Hangar is down and most likely out.

Rob

Brent Robbins

unread,
May 29, 2024, 12:46:03 AM5/29/24
to ope...@googlegroups.com
Rob:

Would you sponsor a less fancy hangar with no visuals?  How about just a file directory?

Hate to see the vsp file library be inaccessible.

Brent

--
You received this message because you are subscribed to the Google Groups "OpenVSP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openvsp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openvsp/9f0a4d7e-0b03-413b-af7e-28bb674b2e7bn%40googlegroups.com.

Rob McDonald

unread,
May 29, 2024, 1:06:45 AM5/29/24
to OpenVSP
I will endorse (but not maintain) something community driven and backed.

We've talked some about setting up a GitHub repository -- I think that is a fine way to go.

I'm happy to connect such a repository to the umbrella OpenVSP GitHub account and give a set of users from the community access to maintain that repository.

The Hangar is more than a cache of *.vsp3 files.  It includes metadata on each file -- the 3D visualization, but also the description and some expression of intent.  Most of that isn't very useful, but I think keeping the authorship and license information with each file is essential.

I think it should be thought through -- for example, someone should plan ahead what the repository directory structure should be.  GitHub has some ability to display 3D files (at least STL).  A nice template README.md in each directory could provide some standard information about the files.  If someone was more advanced than that, then I'm sure something could be auto-generated via GitHub Pages that would render a new website each time a push was made.  If users were required to upload *.x3d files, the rendered 3D visualization could be duplicated on a website.

If someone wants to go this way, they should create a temporary sandbox GitHub repository with just a few files in it and start playing with how they are displayed and how the site works.

Long term, who is going to accept pull requests?  What standard is going to be applied?

The Hangar had less than 1000 files on it -- many of them are for V2.  Most of them are terrible models.  Do we want the future hangar to be a free-for-all like the old one?  Or do we want some level of curation?  If so, who and what standard?

I will support a user-driven initiative that is well thought through and that seems to have some critical mass behind it to see it move forward.  So far I've heard rumblings that mostly sound like "somebody outta...", but I haven't seen any progress.  I know that I do not have the time or interest to do it myself.

I will help recover the old Hangar files and metadata for such an initiative.


That said, I do have interest in setting up a somewhat parallel effort.  I intend the OpenVSP Wind Tunnel to become a repository of test cases for all of the analyses in OpenVSP.  They will serve as unit and system level software tests.  They will also serve as V&V test cases.  They will also serve as tutorials and documentation of best practices.  It is a tall order that I have not had enough time to put to, but I hope this project will set a new standard of transparency for engineering analysis tools.

Rob

Olex Tkachuk

unread,
May 29, 2024, 7:18:13 PM5/29/24
to OpenVSP
I think, it would be great to have a place that users can share own work plus have some standard examples for newcomers to start with.
Reply all
Reply to author
Forward
0 new messages