Visual Studio extension work not so well under subsection script

gaoxinlei · December 11, 2024, 3:56pm

when type parameters outside subsection,it works well, but can not help code completion when in subsection blocks.

this is the example, expect “Model name” but “model” instead.

gassmoeller · December 12, 2024, 12:09pm

Hi @gaoxinlei, sorry to hear the extension is causing trouble for you. I have been using it for a while now and it always seem to work as expected, i.e. the auto-completion inside subsections should work.

In order to find out why it isnt working for you, could you check and post the following items:

The version of your VS code (any version newer than 1.89.1 should work, the most recent one is 1.96.0)
The version of your ASPECT VS code extension (it should show v1.1.3 next to the name of the extension in the VS code extension menu)
Please make sure the file your are working on has the ending .prm
Please check if the extension is activated when you open prm files. In order to that, check if you see the following:
- in the bottom right corner of your VS code, you should see ‘aspect’ show up as the selected ‘Language’ for this file
- In the bottom left or bottom center status bar, you should see text like this: ‘Current aspect version: 2.5.0’ this indicates that the ASPECT extension is active and is using the correct aspect input parameter schema

If all that is the case and you are still having problems, then we will need to think a bit more about it, but for now let me know if all that is working for you.

Best,
Rene

gaoxinlei · December 12, 2024, 4:17pm

Hi, My macbook works well but windows does not.

The version of my VS code :1.95.3
Thre version of my Aspect extension: 1.1.3
file has the ending .prm, right
extension is activated (both checked)

image2196×868 96.8 KB

image396×161 3.23 KB

image390×195 3.38 KB

image591×439 9.34 KB

All checked, here is the effect when coding outside subsection block:

and here is inside subsection:

I want “Model name” this case, but I can only get “model” or “Model” and a word that typed before
BR

gassmoeller · December 13, 2024, 10:18am

Oh, so it may be related to the Windows operating system? I do not know if the VS code extension was extensively tested under Windows, maybe one of the other users of the forum has used it before under Windows?

It may be useful to open an issue report in the repository of the VS code extension here: Issues · Vscode extensions / vscode-aspect · GitLab . This way the developers of the extension will be made aware of the issue (I do not know if they check this forum).

Best,
Rene

gaoxinlei · December 13, 2024, 12:05pm

Thanks a lot, I just open an issue right there and I will track this.
BR

gaoxinlei · January 17, 2025, 12:11pm

Hi , I found this “parameters.xml” from apsect code repository, does it contains all paramaters and subsections?

github.com/geodynamics/aspect

doc/parameter_view/parameters.xml

main

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="application/xml" href="parameters.xsl"?>

<ParameterHandler>
<Additional_20shared_20libraries>
<value/>
<default_value/>
<documentation>
A list of names of additional shared libraries that should be loaded upon starting up the program. The names of these files can contain absolute or relative paths (relative to the directory in which you call ASPECT). In fact, file names that do not contain any directory information (i.e., only the name of a file such as &lt;libmyplugin.so&gt; will not be found if they are not located in one of the directories listed in the \texttt{LD_LIBRARY_PATH} environment variable. In order to load a library in the current directory, use &lt;./libmyplugin.so&gt; instead.

If you specify &lt;./libmyplugin.so&gt;, ASPECT will open either &lt;./libmyplugin.debug.so&gt; or &lt;./libmyplugin.release.so&gt; depending on the current ASPECT build type.

The typical use of this parameter is so that you can implement additional plugins in your own directories, rather than in the ASPECT source directories. You can then simply compile these plugins into a shared library without having to re-compile all of ASPECT. See the section of the manual discussing writing extensions for more information on how to compile additional files into a shared library.
</documentation>
<pattern>
1
</pattern>
<pattern_description>
[List of &lt;[FileName (Type: input)]&gt; of length 0...4294967295 (inclusive)]
</pattern_description>

This file has been truncated. show original

I think I could create a gui through that file, which would list all available parameters and subsections under root or nested subsection. maybe a webpage is suitable for most operating system.

BR

gassmoeller · January 17, 2025, 3:11pm

Hi BR,
Yes that file contains all ASPECT parameters (every ASPECT model you run also creates this file). We already use this file to produce the following website: https://aspect.geodynamics.org/doc/parameter_view/parameters.xml (It is linked from the ASPECT homepage under “Parameters”).
Is this what you had in mind?

gaoxinlei · January 19, 2025, 4:21am

Yeah that is exactly what I need , and it is really helpful, I would make my toolkit myself by it.
thanks a lot !
BR

Topic		Replies	Views
Visual Studio Code extension for ASPECT parameter file (.prm) ASPECT extension	5	285	April 21, 2021
Operational problem ASPECT	2	102	April 9, 2024
Installation on MacOS (Catalina 10.15.6)- Windows style line endings ASPECT installation	3	394	September 28, 2020
Point values for the subsection Postprocess does not work for one of the free surface cases ASPECT	2	240	September 29, 2021
Aspect 2.2.0-pre Docker Container: problem with free-surface subsection ASPECT	2	348	April 22, 2020

Visual Studio extension work not so well under subsection script

Related topics